Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.1255788803100586s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.6842262744903564s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.7380151748657227s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0008518695831298828s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.00047087669372558594s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 7.867813110351562e-06s
INFO | --- Analysis for 2000-us-census-rdf took 6.650245189666748s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.732550859451294s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.001489400863647461s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2615199089050293s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020042896270751953s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.886222839355469e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 6.198883056640625e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.244828224182129s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.38690185546875e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2661769390106201s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.019989013671875s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.6941299438476562e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 9.298324584960938e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.142085552215576s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.3289322853088379s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.2616567611694336s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020203590393066406s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.0001010894775390625s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for abs-linked-data took 2.732147693634033s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 4.4345855712890625e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.00034117698669433594s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.27896952629089355s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.0994415283203125e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 6.4373016357421875e-06s
INFO | --- Analysis for academic-offer-of-unl took 3.302764654159546s
Availability | SPARQL endpoint availability check for AcadOnto took 4.3392181396484375e-05s
Availability | VoID file availability check for AcadOnto took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.24558615684509277s
Reputation | Calculation of the PageRank for AcadOnto took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.0517578125e-05s
Believability | Calculation of trust value for AcadOnto took 7.867813110351562e-06s
INFO | --- Analysis for acadonto took 2.756049156188965s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.563477516174316s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2675626277923584s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.8623809814453125e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for acorn-sat took 37.260305404663086s
Availability | SPARQL endpoint availability check for Addgene took 4.3392181396484375e-05s
Availability | VoID file availability check for Addgene took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Addgene took 0.6896734237670898s
Reputation | Calculation of the PageRank for Addgene took 0.020425081253051758s
Interlinking | Calculation of Degree of Connection for Addgene took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.647804260253906e-05s
Believability | Calculation of trust value for Addgene took 7.62939453125e-06s
INFO | --- Analysis for addgene took 16.78220558166504s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.410743713378906e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2948768138885498s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020125150680541992s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.036064147949219e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 6.9141387939453125e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 9.023958683013916s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.5593926906585693s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.26857805252075195s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.0201570987701416s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.337860107421875e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 7.152557373046875e-06s
INFO | --- Analysis for aemet took 6.028502702713013s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.1484832763671875e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.27201128005981445s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 2.8848648071289062e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 7.152557373046875e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.9113993644714355s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.04015541076660156s
Availability | VoID file availability check for AgriNepalData took 0.00042748451232910156s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2517969608306885s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020175695419311523s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.985664367675781e-05s
Believability | Calculation of trust value for AgriNepalData took 8.344650268554688e-06s
INFO | --- Analysis for agrinepaldata took 2.3497447967529297s
Availability | SPARQL endpoint availability check for AGRIS took 261.7043447494507s
Availability | VoID file availability check for AGRIS took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for AGRIS took 0.2830209732055664s
Reputation | Calculation of the PageRank for AGRIS took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.367134094238281e-05s
Believability | Calculation of trust value for AGRIS took 8.344650268554688e-06s
INFO | --- Analysis for agris took 556.7637624740601s
Availability | SPARQL endpoint availability check for AGROVOC took 4.482269287109375e-05s
Availability | VoID file availability check for AGROVOC took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.7631354331970215s
Reputation | Calculation of the PageRank for AGROVOC took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.8650970458984375e-05s
Believability | Calculation of trust value for AGROVOC took 6.4373016357421875e-06s
INFO | --- Analysis for agrovoc-skos took 3.7747271060943604s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.76837158203125e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.24976634979248047s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 6.4373016357421875e-06s
INFO | --- Analysis for aksworg took 3.7631094455718994s
Availability | SPARQL endpoint availability check for AlchemyAPI took 5.030632019042969e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.24874067306518555s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.9087066650390625e-05s
Believability | Calculation of trust value for AlchemyAPI took 7.62939453125e-06s
INFO | --- Analysis for alchemyapi took 3.2892203330993652s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.3392181396484375e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.26842832565307617s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020430326461791992s
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.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.0517578125e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 6.67572021484375e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.876133441925049s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.6775908470153809s
Availability | VoID file availability check for aliada-scanbit-net took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.24453186988830566s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00012040138244628906s
Believability | Calculation of trust value for aliada-scanbit-net took 7.3909759521484375e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.8716981410980225s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.863739013671875e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.2720448970794678s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.020276546478271484s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 3.7670135498046875e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.9325485229492188e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 7.152557373046875e-06s
INFO | --- Analysis for allen-brain-atlas took 2.8899028301239014s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 4.225849151611328s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0008058547973632812s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.2669713497161865s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.020227432250976562s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 6.866455078125e-05s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 7.3909759521484375e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 21.651840209960938s
Availability | SPARQL endpoint availability check for Alojamientos took 5.125999450683594e-05s
Availability | VoID file availability check for Alojamientos took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.2544713020324707s
Reputation | Calculation of the PageRank for Alojamientos took 0.021364450454711914s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.147125244140625e-05s
Believability | Calculation of trust value for Alojamientos took 1.71661376953125e-05s
INFO | --- Analysis for alojamientos-zaragoza took 2.7908968925476074s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.41486382484436035s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.2552149295806885s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.021208763122558594s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.790855407714844e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 8.344650268554688e-06s
INFO | --- Analysis for alpino-rdf took 3.8214147090911865s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.172325134277344e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.27751636505126953s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 2.86102294921875e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 8.106231689453125e-06s
INFO | --- Analysis for am-collections-online took 2.958775281906128s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.76837158203125e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.2696521282196045s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for amon took 2.9181134700775146s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7602846622467041s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.24148225784301758s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020292043685913086s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 8.869171142578125e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 7.867813110351562e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.8150250911712646s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.38690185546875e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.27493715286254883s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.123283386230469e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 7.62939453125e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.852855920791626s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.410743713378906e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.2518489360809326s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0008778572082519531s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.314018249511719e-05s
Believability | Calculation of trust value for Animal Diversity Web took 8.344650268554688e-06s
INFO | --- Analysis for animal-diversity-web took 2.8276865482330322s
Availability | SPARQL endpoint availability check for apache took 4.482269287109375e-05s
Availability | VoID file availability check for apache took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for apache took 0.2528524398803711s
Reputation | Calculation of the PageRank for apache took 0.0202023983001709s
Interlinking | Calculation of Degree of Connection for apache took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for apache took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for apache took 5.221366882324219e-05s
Believability | Calculation of trust value for apache took 7.152557373046875e-06s
INFO | --- Analysis for apache took 3.2793798446655273s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2611711025238037s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf took 6.726836442947388s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.26360487937927246s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020816802978515625s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.6514410972595215s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.2658259868621826s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020156383514404297s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.619164228439331s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.2960696220397949s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 5.030632019042969e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 9.775161743164062e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.639472007751465s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.2639472484588623s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.486713171005249s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2984011173248291s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020334243774414062s
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.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.6003806591033936s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.26749420166015625s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02023625373840332s
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.0007753372192382812s
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 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.479369640350342s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2717244625091553s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.525864601135254s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2555699348449707s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0008237361907958984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.534234046936035s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2696716785430908s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.497937202453613s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.28257226943969727s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.619044542312622s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.2841956615447998s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.02069377899169922s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.364418029785156e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 24.904322624206543s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 5.173683166503906e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.27807140350341797s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02232646942138672s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0010001659393310547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 5.078315734863281e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 6.116334438323975s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.24056005477905273s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.742895603179932s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 7.319450378417969e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2898378372192383s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020084381103515625s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.6137213706970215s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.9114227294921875e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2613046169281006s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02013397216796875s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.5119469165802s
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.0004487037658691406s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2597165107727051s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.863739013671875e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.493975877761841s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.24849677085876465s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02020740509033203s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.453392505645752s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.6253204345703125e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.25455808639526367s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.543779134750366s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 5.054473876953125e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2872776985168457s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.529984951019287s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2645139694213867s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 5.173683166503906e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.58281683921814s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 7.224082946777344e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.255507230758667s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.61717414855957s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2435925006866455s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 5.9604644775390625e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.197848320007324s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.825092077255249s
Availability | VoID file availability check for AragoDBPedia took 0.0005509853363037109s
Extra | Recovery of all triples for AragoDBPedia took 7.529873847961426s
Performance | Total latancy measurement for AragoDBPedia took 1.9454259872436523s
Amount of data | Number of triples check for AragoDBPedia took 1.065969705581665s
Interoperability | New terms check for AragoDBPedia took 2.7965664863586426s
Versatility | Languages check for AragoDBPedia took 60.515177726745605s
Interpretability | Number of blank nodes check for AragoDBPedia took 5.5906829833984375s
Security | Check HTTPS for AragoDBPedia took 0.2478780746459961s
Interpretability | RDF structures check for AragoDBPedia took 1.0893399715423584s
Versatility | Serialization formats check for AragoDBPedia took 1.4074454307556152s
Availability | RDF dump link check for AragoDBPedia took 0.4427366256713867s
License | MR license check for AragoDBPedia took 0.7056360244750977s
License | HR license check for AragoDBPedia took 6.894437074661255s
Amount of data | Number of property check for AragoDBPedia took 0.4305706024169922s
Understandability | Number of label check for AragoDBPedia took 0.6770195960998535s
Understandability | URI regex check for AragoDBPedia took 0.9145834445953369s
Understandability | Vocabs check for AragoDBPedia took 0.48648786544799805s
Verifiability | Authors check for AragoDBPedia took 0.5380105972290039s
Verifiability | Publishers check for AragoDBPedia took 0.4038729667663574s
Performance | Throughput check for AragoDBPedia took 11.875155687332153s
Amount of data | Check the number of entities for AragoDBPedia took 7.43865966796875e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.5181369781494141s
Interlinking | sameAs chians check for AragoDBPedia took 0.42281365394592285s
Interlinking | skos check for AragoDBPedia took 0.687187910079956s
Interlinking | skos check for AragoDBPedia took 0.37885618209838867s
Timeliness | dataset update frequency check for AragoDBPedia took 1.0101864337921143s
Currency | Creation date check for AragoDBPedia took 2.0762712955474854s
Currency | Modification date check for AragoDBPedia took 0.9575345516204834s
Rep.Conc. | URIs length for AragoDBPedia took 6.83898401260376s
Interoperability | New vocabularies check for AragoDBPedia took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.3829786777496338s
Accuracy | Check Functional Property for AragoDBPedia took 0.48099374771118164s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.47736501693725586s
Accuracy | Check Empty annotation labels for AragoDBPedia took 2.0508835315704346s
Accuracy | Check White space in annotation for AragoDBPedia took 0.030797958374023438s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.02878284454345703s
Consistency | Disjoint class check for AragoDBPedia took 0.5770800113677979s
Consistency | Check Misplaced properties for AragoDBPedia took 4.708252191543579s
Consistency | Misplaced classes for AragoDBPedia took 0.6100842952728271s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.6610493659973145s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3508825302124023s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.473439455032349s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03160905838012695s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.5617151260375977s
Security | Sign check for AragoDBPedia took 0.616530179977417s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3254.1911404132843s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.5199663639068604s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.023533344268798828s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 3.147125244140625e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.430511474609375e-06s
Believability | Calculation of trust value for AragoDBPedia took 6.198883056640625e-06s
INFO | --- Analysis for aragodbpedia took 13521.63483953476s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.268646717071533s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.25231337547302246s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020867347717285156s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.792213439941406e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for archiveshub-linkeddata took 84.65875267982483s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.1961669921875e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.6918857097625732s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 2.9325485229492188e-05s
Believability | Calculation of trust value for Archivi ISMA took 7.62939453125e-06s
INFO | --- Analysis for archivio-isma took 4.182966709136963s
Availability | SPARQL endpoint availability check for ARIADNE took 4.267692565917969e-05s
Availability | VoID file availability check for ARIADNE took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.27522969245910645s
Reputation | Calculation of the PageRank for ARIADNE took 0.020811796188354492s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 2.9087066650390625e-05s
Believability | Calculation of trust value for ARIADNE took 7.152557373046875e-06s
INFO | --- Analysis for ariadne took 2.910285711288452s
Availability | SPARQL endpoint availability check for Aristotle University took 4.172325134277344e-05s
Availability | VoID file availability check for Aristotle University took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.26380228996276855s
Reputation | Calculation of the PageRank for Aristotle University took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 2.9087066650390625e-05s
Believability | Calculation of trust value for Aristotle University took 7.62939453125e-06s
INFO | --- Analysis for aristotle-university took 2.8474395275115967s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.8838067054748535s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.27614855766296387s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.0279159545898438e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 7.62939453125e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 19.80938410758972s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.220008850097656e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.2664225101470947s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 7.62939453125e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.8998405933380127s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.9273927211761475s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.2579963207244873s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.8623809814453125e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 8.344650268554688e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.69298243522644s
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.0007085800170898438s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.2698965072631836s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.021332740783691406s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010561943054199219s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 11.639019012451172s
Availability | SPARQL endpoint availability check for Arthroscopy community took 6.079673767089844e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.25049424171447754s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00011873245239257812s
Believability | Calculation of trust value for Arthroscopy community took 1.049041748046875e-05s
INFO | --- Analysis for arthroscopy took 11.254532098770142s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 8.130073547363281e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.25202012062072754s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.866455078125e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.1205673217773438e-05s
INFO | --- Analysis for asit took 9.662456035614014s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.601478576660156e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2578697204589844s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.021006107330322266s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.9577484130859375e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.0728836059570312e-05s
INFO | --- Analysis for asjp took 5.238668441772461s
Availability | SPARQL endpoint availability check for ASN:US took 1.8659090995788574s
Availability | VoID file availability check for ASN:US took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for ASN:US took 0.26843881607055664s
Reputation | Calculation of the PageRank for ASN:US took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.866455078125e-05s
Believability | Calculation of trust value for ASN:US took 6.67572021484375e-06s
INFO | --- Analysis for asn-us took 12.81576418876648s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.506111145019531e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.27876996994018555s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.361701965332031e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 6.67572021484375e-06s
INFO | --- Analysis for aspire-mmu took 4.423780202865601s
Availability | SPARQL endpoint availability check for associations took 4.363059997558594e-05s
Availability | VoID file availability check for associations took 0.0007874965667724609s
Completeness | Calculation of interlinking completeness for associations took 0.2507917881011963s
Reputation | Calculation of the PageRank for associations took 0.020983457565307617s
Interlinking | Calculation of Degree of Connection for associations took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for associations took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for associations took 6.985664367675781e-05s
Believability | Calculation of trust value for associations took 8.344650268554688e-06s
INFO | --- Analysis for associations took 7.11551308631897s
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.00026917457580566406s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2610929012298584s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.147125244140625e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 3.6716461181640625e-05s
INFO | --- Analysis for atc-publikovan--s-kl took 2.8694441318511963s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.38690185546875e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.28252363204956055s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020926475524902344s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.036064147949219e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 7.62939453125e-06s
INFO | --- Analysis for athelia-rfid took 5.263901472091675s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 5.245208740234375e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.26648736000061035s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.170967102050781e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 9.059906005859375e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.8718929290771484s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6173098087310791s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.27112507820129395s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020787954330444336s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.845329284667969e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 9.775161743164062e-06s
INFO | --- Analysis for austrian_ski_racers took 3.7975361347198486s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3061978816986084s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0011107921600341797s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 186.34452199935913s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5178961753845215s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0091767311096s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 251.06546354293823s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0851299762726s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0423195362091s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23042011260986328s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24231672286987305s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1947464942932129s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15252423286437988s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 59.41508889198303s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0188207626343s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16411733627319336s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0433876514435s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24822115898132324s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11103510856628418s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11354660987854004s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12160754203796387s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.61782431602478s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.700920104980469e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10488629341125488s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06127738952637s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16225123405456543s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15051913261413574s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15607905387878418s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.27771496772766113s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23374152183532715s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 726.4210052490234s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13800311088562012s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.73258352279663s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.2804031372070312s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.9364800453186035s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13151979446411133s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1643691062927s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 67.57621836662292s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.4774999618530273s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.52242612838745s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.8376903533935547s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21597552299499512s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.153655767440796s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1771814823150635s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021288156509399414s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.343292236328125e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.9073486328125e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.4836273193359375e-06s
INFO | --- Analysis for b3kat took 4362.008249998093s
Availability | SPARQL endpoint availability check for BabelNet took 0.5216343402862549s
Availability | VoID file availability check for BabelNet took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for BabelNet took 0.7063674926757812s
Reputation | Calculation of the PageRank for BabelNet took 0.025820255279541016s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0008752346038818359s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00018143653869628906s
Believability | Calculation of trust value for BabelNet took 8.106231689453125e-06s
INFO | --- Analysis for babelnet took 5.634439945220947s
Availability | SPARQL endpoint availability check for BAMS took 5.364418029785156e-05s
Availability | VoID file availability check for BAMS took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for BAMS took 0.25299859046936035s
Reputation | Calculation of the PageRank for BAMS took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for BAMS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.123283386230469e-05s
Believability | Calculation of trust value for BAMS took 6.67572021484375e-06s
INFO | --- Analysis for bams took 2.87856125831604s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 5.1021575927734375e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2679634094238281s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.076957702636719e-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 3.7365472316741943s
Availability | SPARQL endpoint availability check for BBC Music took 0.2868955135345459s
Availability | VoID file availability check for BBC Music took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for BBC Music took 0.25577330589294434s
Reputation | Calculation of the PageRank for BBC Music took 0.02096390724182129s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013756752014160156s
Believability | Calculation of trust value for BBC Music took 5.7220458984375e-06s
INFO | --- Analysis for bbc-music took 3.2552366256713867s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.3833119869232178s
Availability | VoID file availability check for BBC Programmes took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2820894718170166s
Reputation | Calculation of the PageRank for BBC Programmes took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010466575622558594s
Believability | Calculation of trust value for BBC Programmes took 8.106231689453125e-06s
INFO | --- Analysis for bbc-programmes took 10.47412896156311s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.26802825927734375s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2549586296081543s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.021137237548828125s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00012302398681640625s
Believability | Calculation of trust value for BBC Wildlife Finder took 6.198883056640625e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.464462995529175s
Availability | SPARQL endpoint availability check for BBOP took 4.315376281738281e-05s
Availability | VoID file availability check for BBOP took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for BBOP took 0.27850890159606934s
Reputation | Calculation of the PageRank for BBOP took 0.02027130126953125s
Interlinking | Calculation of Degree of Connection for BBOP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBOP took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.9325485229492188e-05s
Believability | Calculation of trust value for BBOP took 7.152557373046875e-06s
INFO | --- Analysis for bbop took 2.9118690490722656s
Availability | SPARQL endpoint availability check for BBOP took 4.363059997558594e-05s
Availability | VoID file availability check for BBOP took 0.0008389949798583984s
Completeness | Calculation of interlinking completeness for BBOP took 0.2632009983062744s
Reputation | Calculation of the PageRank for BBOP took 0.020432472229003906s
Interlinking | Calculation of Degree of Connection for BBOP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.075599670410156e-05s
Believability | Calculation of trust value for BBOP took 7.152557373046875e-06s
INFO | --- Analysis for bbop-selected took 20.973254680633545s
Availability | SPARQL endpoint availability check for Bdgp took 1.7389612197875977s
Availability | VoID file availability check for Bdgp took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for Bdgp took 0.6954917907714844s
Reputation | Calculation of the PageRank for Bdgp took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for Bdgp took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bdgp took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bdgp took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bdgp took 6.4373016357421875e-06s
INFO | --- Analysis for bdgp took 8.831850051879883s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 0.1651003360748291s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.245955228805542s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.437301635742188e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 5.4836273193359375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 2.668992280960083s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 6.914138793945312e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0003039836883544922s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.2537555694580078s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020973682403564453s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.170967102050781e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 9.298324584960938e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.9160633087158203s
Availability | SPARQL endpoint availability check for berlios took 4.38690185546875e-05s
Availability | VoID file availability check for berlios took 0.0003342628479003906s
Completeness | Calculation of interlinking completeness for berlios took 0.2717406749725342s
Reputation | Calculation of the PageRank for berlios took 0.021691083908081055s
Interlinking | Calculation of Degree of Connection for berlios took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for berlios took 9.584426879882812e-05s
Believability | Calculation of trust value for berlios took 7.867813110351562e-06s
INFO | --- Analysis for berlios took 2.7705113887786865s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.39963817596435547s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.25192785263061523s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.559226989746094e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for bfs-linked-data took 2.9004344940185547s
Availability | SPARQL endpoint availability check for BibBase took 0.08559131622314453s
Availability | VoID file availability check for BibBase took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for BibBase took 0.2665894031524658s
Reputation | Calculation of the PageRank for BibBase took 0.020358800888061523s
Interlinking | Calculation of Degree of Connection for BibBase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.1552734375e-05s
Believability | Calculation of trust value for BibBase took 7.3909759521484375e-06s
INFO | --- Analysis for bibbase took 2.488943338394165s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.458427429199219e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.2541067600250244s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.0001163482666015625s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 7.152557373046875e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 8.229394435882568s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.3392181396484375e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.2591376304626465s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02987360954284668s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0014190673828125s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.0001385211944580078s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 8.58306884765625e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 7.813578844070435s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.4345855712890625e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.25084590911865234s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.845357656478882s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.363059997558594e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2547028064727783s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.02176666259765625s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.8848648071289062e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.1205673217773438e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 4.83602237701416s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 5.3882598876953125e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0003209114074707031s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2638058662414551s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020282983779907227s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.9325485229492188e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 5.9604644775390625e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.448514938354492s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.26878786087036133s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 5.7220458984375e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.8824620246887207s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.2812039852142334s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006306171417236328s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 21.408219814300537s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.509331464767456s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 46.05162858963013s
Interoperability | New terms check for Bio2RDF::Affymetrix took 47.23188066482544s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.12246012687683s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.1419205665588379s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.678131103515625s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.1924586296081543s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 0.1714155673980713s
License | MR license check for Bio2RDF::Affymetrix took 0.29773497581481934s
License | HR license check for Bio2RDF::Affymetrix took 60.095558643341064s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.13901448249816895s
Understandability | Number of label check for Bio2RDF::Affymetrix took 10.382598876953125s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.38105106353759766s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.12759780883789062s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.15329861640930176s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.12375783920288086s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.745502710342407s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 76.56262731552124s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.5986638069152832s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2108011245727539s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.8870539665222168s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.2539825439453125s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.1106576919555664s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2829551696777344s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.23248910903930664s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 110.92086124420166s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 13.479204654693604s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.32047390937805176s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15457773208618164s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.1252884864807129s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.416576862335205s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.9110288619995117s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.684581995010376s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.262692928314209s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.09696221351624s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.3675529956817627s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.675710201263428s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3728854656219482s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.408331871032715s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7072296142578125s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3173995018005371s
Security | Sign check for Bio2RDF::Affymetrix took 0.12155032157897949s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 11.234645128250122s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 1.2949702739715576s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.021022319793701172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.465217590332031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 12.759438753128052s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 1043.9041488170624s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5212790966033936s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0007104873657226562s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 19.936229705810547s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2317609786987305s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 46.361677408218384s
Interoperability | New terms check for Bio2RDF::Biomodels took 43.57811975479126s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25643062591553s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.25862598419189453s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.16850805282592773s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.82002854347229s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.3265573978424072s
Availability | RDF dump link check for Bio2RDF::Biomodels took 0.2932858467102051s
License | MR license check for Bio2RDF::Biomodels took 0.4362764358520508s
License | HR license check for Bio2RDF::Biomodels took 60.234036922454834s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.2703070640563965s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.138792753219604s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5539402961730957s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2836761474609375s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.2642021179199219s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.26813173294067383s
Performance | Throughput check for Bio2RDF::Biomodels took 10.775580406188965s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 75.65525794029236s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.6084907054901123s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.3291289806365967s
Interlinking | skos check for Bio2RDF::Biomodels took 1.2322039604187012s
Interlinking | skos check for Bio2RDF::Biomodels took 0.46921420097351074s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2853207588195801s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5240662097930908s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5439445972442627s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 113.12168955802917s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 13.241111755371094s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.43090224266052246s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.292435884475708s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2788887023925781s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.199634790420532s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9039716720581055s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6755733489990234s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.3748664855957031s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.49658870697021s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.4409823417663574s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.60359787940979s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3090739250183105s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.62281537055969s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7173454761505127s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.4451942443847656s
Security | Sign check for Bio2RDF::Biomodels took 0.2743844985961914s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 11.630270004272461s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.9771342277526855s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00010848045349121094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 12.047248125076294s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1050.0515806674957s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 7.557868957519531e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.2633798122406006s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 5.10949969291687s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.49824047088623047s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0004451274871826172s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 19.745831966400146s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2685778141021729s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 45.06206750869751s
Interoperability | New terms check for Bio2RDF::Bioportal took 43.15311312675476s
Versatility | Languages check for Bio2RDF::Bioportal took 60.255704164505005s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2581202983856201s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.17432928085327148s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.7786133289337158s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3390331268310547s
Availability | RDF dump link check for Bio2RDF::Bioportal took 0.293520450592041s
License | MR license check for Bio2RDF::Bioportal took 0.40248847007751465s
License | HR license check for Bio2RDF::Bioportal took 60.23759961128235s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.25932860374450684s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.185491800308228s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5732216835021973s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2530834674835205s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2747037410736084s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.26601672172546387s
Performance | Throughput check for Bio2RDF::Bioportal took 11.240957498550415s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 75.97660994529724s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.7420356273651123s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3198072910308838s
Interlinking | skos check for Bio2RDF::Bioportal took 0.9381821155548096s
Interlinking | skos check for Bio2RDF::Bioportal took 0.37137770652770996s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2588963508605957s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5146844387054443s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5041794776916504s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 113.06556463241577s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 11.758904695510864s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4375128746032715s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.2677135467529297s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2868165969848633s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.26317286491394s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.9048364162445068s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6572380065917969s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.38819122314453125s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.6644356250763s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4032318592071533s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 7.312566041946411s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3261761665344238s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.575711250305176s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.6986167430877686s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.428386926651001s
Security | Sign check for Bio2RDF::Bioportal took 0.29595446586608887s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 11.526193618774414s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.8604109287261963s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004794597625732422s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 12.203240633010864s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-bioportal took 1048.8993561267853s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.13636398315429688s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.2913980484008789s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020073652267456055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.412101745605469e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-chembl took 18.276448249816895s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.4807109832763672s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006420612335205078s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 19.39088535308838s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2119653224945068s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 52.0745632648468s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 41.738818407058716s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.25026321411133s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2721071243286133s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.16116952896118164s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.4746580123901367s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.34813475608825684s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 0.31185245513916016s
License | MR license check for Bio2RDF::Clinicaltrials took 0.5028390884399414s
License | HR license check for Bio2RDF::Clinicaltrials took 60.252540588378906s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.27814650535583496s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.578346490859985s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5850076675415039s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.2477879524230957s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.27126383781433105s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.2796061038970947s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.041313409805298s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 75.1158652305603s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 1.1134209632873535s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.35146045684814453s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7579340934753418s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3859081268310547s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.26921796798706055s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5188491344451904s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.532923698425293s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 108.61592292785645s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 11.723966598510742s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.44313836097717285s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2611501216888428s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2646217346191406s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.840181827545166s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.9002523422241211s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6517300605773926s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.36434245109558105s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.13102698326111s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.408464193344116s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.901935577392578s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.365041971206665s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.623082637786865s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7015609741210938s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4449150562286377s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2675292491912842s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 11.346478700637817s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.9478123188018799s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.022047996520996094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 0.00011849403381347656s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 13.14813494682312s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1036.6544568538666s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.44562673568725586s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005972385406494141s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.52452516555786s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2233378887176514s
Amount of data | Number of triples check for Bio2RDF::Ctd took 43.8204927444458s
Interoperability | New terms check for Bio2RDF::Ctd took 40.90827465057373s
Versatility | Languages check for Bio2RDF::Ctd took 60.248284578323364s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.27797770500183105s
Security | Check HTTPS for Bio2RDF::Ctd took 0.14726042747497559s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.39589500427246094s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.307340145111084s
Availability | RDF dump link check for Bio2RDF::Ctd took 0.2983427047729492s
License | MR license check for Bio2RDF::Ctd took 0.434661865234375s
License | HR license check for Bio2RDF::Ctd took 60.257163286209106s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2832908630371094s
Understandability | Number of label check for Bio2RDF::Ctd took 9.849237203598022s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5796873569488525s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.24639225006103516s
Verifiability | Authors check for Bio2RDF::Ctd took 0.25942468643188477s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.25139951705932617s
Performance | Throughput check for Bio2RDF::Ctd took 11.288146495819092s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 78.501957654953s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.596510648727417s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.33196401596069336s
Interlinking | skos check for Bio2RDF::Ctd took 0.7997562885284424s
Interlinking | skos check for Bio2RDF::Ctd took 0.3304457664489746s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2399892807006836s
Currency | Creation date check for Bio2RDF::Ctd took 0.5029489994049072s
Currency | Modification date check for Bio2RDF::Ctd took 0.47955322265625s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 108.41606855392456s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 13.25731110572815s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4238245487213135s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.29161739349365234s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.27530837059020996s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.137832403182983s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.894428014755249s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6791207790374756s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.39595484733581543s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.38009262084961s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.4164958000183105s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.190989971160889s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3621692657470703s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.60225439071655s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7190022468566895s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.42398738861083984s
Security | Sign check for Bio2RDF::Ctd took 0.2763538360595703s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 11.55772876739502s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 1.327627182006836s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 12.99905252456665s
Believability | Calculation of trust value for Bio2RDF::Ctd took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-ctd took 1037.5347292423248s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.482269287109375e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.6973638534545898s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.1021575927734375e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-dataset took 3.9447999000549316s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.48240137100219727s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005710124969482422s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 20.054739713668823s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2355799674987793s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 43.60583806037903s
Interoperability | New terms check for Bio2RDF::Dbsnp took 42.5759117603302s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.22581362724304s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.26241278648376465s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.15422749519348145s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.3397386074066162s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.30916714668273926s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 0.3007657527923584s
License | MR license check for Bio2RDF::Dbsnp took 0.5843410491943359s
License | HR license check for Bio2RDF::Dbsnp took 60.247827768325806s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.25227904319763184s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.190122604370117s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.6010730266571045s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.25402283668518066s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.26677942276000977s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.2475752830505371s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.398084163665771s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 74.2024188041687s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.578779935836792s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3414633274078369s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.7283389568328857s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.4214658737182617s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.25134706497192383s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.4961221218109131s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.4981098175048828s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 108.03672051429749s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 13.204112529754639s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.42677879333496094s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2609529495239258s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2647819519042969s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.570247411727905s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.9230895042419434s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6789531707763672s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.380969762802124s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 64.97378778457642s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.409402847290039s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.348460674285889s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3483846187591553s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.540467500686646s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7051734924316406s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.4674351215362549s
Security | Sign check for Bio2RDF::Dbsnp took 0.2599976062774658s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 12.085124254226685s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.9916181564331055s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 11.704077005386353s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1078.3779230117798s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4834620952606201s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0007941722869873047s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 22.01219892501831s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2677595615386963s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 43.792906761169434s
Interoperability | New terms check for Bio2RDF::Drugbank took 42.658079862594604s
Versatility | Languages check for Bio2RDF::Drugbank took 60.246187686920166s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2931556701660156s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.16149067878723145s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.43651533126831055s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3364853858947754s
Availability | RDF dump link check for Bio2RDF::Drugbank took 0.3160879611968994s
License | MR license check for Bio2RDF::Drugbank took 0.45284509658813477s
License | HR license check for Bio2RDF::Drugbank took 60.26529860496521s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.26689672470092773s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.370646715164185s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.6297245025634766s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.29655003547668457s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2974278926849365s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.28016066551208496s
Performance | Throughput check for Bio2RDF::Drugbank took 11.213081359863281s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 74.75608682632446s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.803443193435669s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.36415672302246094s
Interlinking | skos check for Bio2RDF::Drugbank took 0.9407949447631836s
Interlinking | skos check for Bio2RDF::Drugbank took 0.3634757995605469s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.24927115440368652s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5178482532501221s
Currency | Modification date check for Bio2RDF::Drugbank took 0.4956235885620117s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 110.60109114646912s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 13.077473163604736s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.42003679275512695s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.28216052055358887s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2532069683074951s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.192723512649536s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.9111344814300537s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6727042198181152s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.3768632411956787s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.6455340385437s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.427783250808716s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.748620986938477s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3578197956085205s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.57151985168457s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7047288417816162s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.42865562438964844s
Security | Sign check for Bio2RDF::Drugbank took 0.2714405059814453s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 11.752527952194214s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.9247190952301025s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010156631469726562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 11.516169786453247s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1038.0670981407166s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.4780857563018799s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006725788116455078s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.704875469207764s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2458815574645996s
Amount of data | Number of triples check for Bio2RDF::Genage took 43.34091377258301s
Interoperability | New terms check for Bio2RDF::Genage took 40.92815542221069s
Versatility | Languages check for Bio2RDF::Genage took 60.24000930786133s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2658534049987793s
Security | Check HTTPS for Bio2RDF::Genage took 0.15583038330078125s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.611030101776123s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.31473326683044434s
Availability | RDF dump link check for Bio2RDF::Genage took 0.28696227073669434s
License | MR license check for Bio2RDF::Genage took 0.43580055236816406s
License | HR license check for Bio2RDF::Genage took 60.2396342754364s
Amount of data | Number of property check for Bio2RDF::Genage took 0.27269816398620605s
Understandability | Number of label check for Bio2RDF::Genage took 9.584685564041138s
Understandability | URI regex check for Bio2RDF::Genage took 0.5703887939453125s
Understandability | Vocabs check for Bio2RDF::Genage took 0.25976085662841797s
Verifiability | Authors check for Bio2RDF::Genage took 0.256650447845459s
Verifiability | Publishers check for Bio2RDF::Genage took 0.2551004886627197s
Performance | Throughput check for Bio2RDF::Genage took 11.046377420425415s
Amount of data | Check the number of entities for Bio2RDF::Genage took 76.48711037635803s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.5828397274017334s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3375732898712158s
Interlinking | skos check for Bio2RDF::Genage took 0.6334085464477539s
Interlinking | skos check for Bio2RDF::Genage took 0.34438371658325195s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2636275291442871s
Currency | Creation date check for Bio2RDF::Genage took 0.5307700634002686s
Currency | Modification date check for Bio2RDF::Genage took 0.5154025554656982s
Rep.Conc. | URIs length for Bio2RDF::Genage took 109.44615435600281s
Interoperability | New vocabularies check for Bio2RDF::Genage took 12.30112361907959s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.43966197967529297s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.28002405166625977s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.2793436050415039s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.304971933364868s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.9138376712799072s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6601383686065674s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4103226661682129s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.57207608222961s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.4244585037231445s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.158620834350586s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3179528713226318s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.555596590042114s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7192227840423584s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.4168877601623535s
Security | Sign check for Bio2RDF::Genage took 0.25605130195617676s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 12.109160900115967s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.9058992862701416s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020575284957885742s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 12.504088163375854s
Believability | Calculation of trust value for Bio2RDF::Genage took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-genage took 1028.9280772209167s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 5.507469177246094e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.6945316791534424s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.936622619628906e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-genbank took 3.7171645164489746s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.4712216854095459s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006451606750488281s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.67808485031128s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.230499267578125s
Amount of data | Number of triples check for Bio2RDF::Gendr took 44.00487780570984s
Interoperability | New terms check for Bio2RDF::Gendr took 43.330525398254395s
Versatility | Languages check for Bio2RDF::Gendr took 60.243403911590576s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.27417945861816406s
Security | Check HTTPS for Bio2RDF::Gendr took 0.1675574779510498s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.8284933567047119s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.33391857147216797s
Availability | RDF dump link check for Bio2RDF::Gendr took 0.27913808822631836s
License | MR license check for Bio2RDF::Gendr took 0.40589046478271484s
License | HR license check for Bio2RDF::Gendr took 60.24999976158142s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.2755246162414551s
Understandability | Number of label check for Bio2RDF::Gendr took 9.490485906600952s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5850558280944824s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2660031318664551s
Verifiability | Authors check for Bio2RDF::Gendr took 0.2747771739959717s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2726254463195801s
Performance | Throughput check for Bio2RDF::Gendr took 10.834525108337402s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 76.42072200775146s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.7551302909851074s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3400256633758545s
Interlinking | skos check for Bio2RDF::Gendr took 0.9364502429962158s
Interlinking | skos check for Bio2RDF::Gendr took 0.34346461296081543s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2773730754852295s
Currency | Creation date check for Bio2RDF::Gendr took 0.5403389930725098s
Currency | Modification date check for Bio2RDF::Gendr took 0.5086774826049805s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 108.7535629272461s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 12.219382524490356s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.45212292671203613s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.28734850883483887s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2747039794921875s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.095260143280029s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.9068124294281006s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6721377372741699s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.45955848693847656s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.11517000198364s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.472691297531128s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.836387395858765s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3660507202148438s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.55462169647217s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7012686729431152s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.4399688243865967s
Security | Sign check for Bio2RDF::Gendr took 0.2664146423339844s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 12.220344305038452s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 1.3097686767578125s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02065443992614746s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 6.198883056640625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 13.575835943222046s
Believability | Calculation of trust value for Bio2RDF::Gendr took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-gendr took 1035.0876288414001s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4742915630340576s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006506443023681641s
Extra | Recovery of all triples for Bio2RDF::Goa took 19.001744270324707s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.220191478729248s
Amount of data | Number of triples check for Bio2RDF::Goa took 44.07098841667175s
Interoperability | New terms check for Bio2RDF::Goa took 40.9455029964447s
Versatility | Languages check for Bio2RDF::Goa took 60.23534536361694s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.28819704055786133s
Security | Check HTTPS for Bio2RDF::Goa took 0.1533656120300293s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.3904294967651367s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3137688636779785s
Availability | RDF dump link check for Bio2RDF::Goa took 0.28953123092651367s
License | MR license check for Bio2RDF::Goa took 0.5774133205413818s
License | HR license check for Bio2RDF::Goa took 60.25825500488281s
Amount of data | Number of property check for Bio2RDF::Goa took 0.24306035041809082s
Understandability | Number of label check for Bio2RDF::Goa took 9.572517156600952s
Understandability | URI regex check for Bio2RDF::Goa took 0.5731813907623291s
Understandability | Vocabs check for Bio2RDF::Goa took 0.24394702911376953s
Verifiability | Authors check for Bio2RDF::Goa took 0.2630612850189209s
Verifiability | Publishers check for Bio2RDF::Goa took 0.25916171073913574s
Performance | Throughput check for Bio2RDF::Goa took 11.256915092468262s
Amount of data | Check the number of entities for Bio2RDF::Goa took 71.72757005691528s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.6043164730072021s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3333420753479004s
Interlinking | skos check for Bio2RDF::Goa took 0.7312536239624023s
Interlinking | skos check for Bio2RDF::Goa took 0.349473237991333s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2386000156402588s
Currency | Creation date check for Bio2RDF::Goa took 0.51688551902771s
Currency | Modification date check for Bio2RDF::Goa took 0.5123069286346436s
Rep.Conc. | URIs length for Bio2RDF::Goa took 110.50347256660461s
Interoperability | New vocabularies check for Bio2RDF::Goa took 12.360403537750244s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.44551753997802734s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.28028059005737305s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.2831857204437256s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.300528049468994s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.911632776260376s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6655967235565186s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.45459771156311035s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.83578872680664s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.437065362930298s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.482299327850342s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3309054374694824s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.57973909378052s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7036230564117432s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.4027388095855713s
Security | Sign check for Bio2RDF::Goa took 0.26837968826293945s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 12.019809007644653s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 1.1776585578918457s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.0207827091217041s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.341934204101562e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 12.151795864105225s
Believability | Calculation of trust value for Bio2RDF::Goa took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-goa took 1034.0238285064697s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.47461628913879395s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006403923034667969s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 19.645108699798584s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2392282485961914s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 43.486849546432495s
Interoperability | New terms check for Bio2RDF::Hgnc took 44.081459045410156s
Versatility | Languages check for Bio2RDF::Hgnc took 60.25165939331055s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.26587438583374023s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.14445877075195312s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.5565240383148193s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.307065486907959s
Availability | RDF dump link check for Bio2RDF::Hgnc took 0.294708251953125s
License | MR license check for Bio2RDF::Hgnc took 0.645176887512207s
License | HR license check for Bio2RDF::Hgnc took 60.25870966911316s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2585310935974121s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.587684392929077s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5560851097106934s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.24898076057434082s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.2563350200653076s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.24808001518249512s
Performance | Throughput check for Bio2RDF::Hgnc took 11.380653142929077s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 75.25103950500488s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.9462566375732422s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.35424208641052246s
Interlinking | skos check for Bio2RDF::Hgnc took 0.7960319519042969s
Interlinking | skos check for Bio2RDF::Hgnc took 0.32971930503845215s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2577481269836426s
Currency | Creation date check for Bio2RDF::Hgnc took 0.501549482345581s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5031497478485107s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.85228085517883s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 12.627978563308716s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.45592522621154785s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.28262805938720703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.28341102600097656s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.488003730773926s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.9032247066497803s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6580393314361572s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.41913270950317383s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.2919647693634s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.4075069427490234s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.2338457107543945s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3194921016693115s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.58482789993286s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7257602214813232s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.41077184677124023s
Security | Sign check for Bio2RDF::Hgnc took 0.27400803565979004s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 12.87089729309082s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.9555628299713135s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011348724365234375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 13.486483097076416s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1034.4502139091492s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.46291446685791016s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006361007690429688s
Extra | Recovery of all triples for Bio2RDF::Homologene took 18.596824407577515s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2831478118896484s
Amount of data | Number of triples check for Bio2RDF::Homologene took 44.056199073791504s
Interoperability | New terms check for Bio2RDF::Homologene took 40.70048689842224s
Versatility | Languages check for Bio2RDF::Homologene took 60.25572991371155s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.27657032012939453s
Security | Check HTTPS for Bio2RDF::Homologene took 0.16661334037780762s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.5378999710083008s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.3247663974761963s
Availability | RDF dump link check for Bio2RDF::Homologene took 0.29068899154663086s
License | MR license check for Bio2RDF::Homologene took 0.4592318534851074s
License | HR license check for Bio2RDF::Homologene took 60.24817633628845s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.27550196647644043s
Understandability | Number of label check for Bio2RDF::Homologene took 10.237195491790771s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5862178802490234s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.23716402053833008s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2755260467529297s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.2677478790283203s
Performance | Throughput check for Bio2RDF::Homologene took 11.219326496124268s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 73.16038274765015s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.6022734642028809s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.3289663791656494s
Interlinking | skos check for Bio2RDF::Homologene took 0.737415075302124s
Interlinking | skos check for Bio2RDF::Homologene took 0.3775458335876465s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.26721739768981934s
Currency | Creation date check for Bio2RDF::Homologene took 0.4985330104827881s
Currency | Modification date check for Bio2RDF::Homologene took 0.4989292621612549s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 108.2123966217041s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 12.519047975540161s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4210474491119385s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.27556800842285156s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.2651214599609375s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.44666051864624s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.9052150249481201s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6649510860443115s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.4347360134124756s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.49965763092041s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4180307388305664s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.471372604370117s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3549437522888184s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.5868661403656s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7184956073760986s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.41178059577941895s
Security | Sign check for Bio2RDF::Homologene took 0.2734360694885254s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 12.095676183700562s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.9129178524017334s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 12.3489990234375s
Believability | Calculation of trust value for Bio2RDF::Homologene took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-homologene took 1033.8805723190308s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.000244140625s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.7263088226318359s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020877838134765625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-inoh took 5.14935040473938s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.48685717582702637s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006251335144042969s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.992023706436157s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2889361381530762s
Amount of data | Number of triples check for Bio2RDF::Interpro took 43.97125744819641s
Interoperability | New terms check for Bio2RDF::Interpro took 40.66752862930298s
Versatility | Languages check for Bio2RDF::Interpro took 60.25871467590332s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2674429416656494s
Security | Check HTTPS for Bio2RDF::Interpro took 0.15764164924621582s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.3201870918273926s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.30017542839050293s
Availability | RDF dump link check for Bio2RDF::Interpro took 0.30437612533569336s
License | MR license check for Bio2RDF::Interpro took 0.45657944679260254s
License | HR license check for Bio2RDF::Interpro took 60.246716022491455s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2547738552093506s
Understandability | Number of label check for Bio2RDF::Interpro took 9.794517278671265s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5936086177825928s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.25577235221862793s
Verifiability | Authors check for Bio2RDF::Interpro took 0.24048137664794922s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.27889275550842285s
Performance | Throughput check for Bio2RDF::Interpro took 11.062570333480835s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 77.49422240257263s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.5937526226043701s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.37474822998046875s
Interlinking | skos check for Bio2RDF::Interpro took 0.8230876922607422s
Interlinking | skos check for Bio2RDF::Interpro took 0.3827250003814697s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2378981113433838s
Currency | Creation date check for Bio2RDF::Interpro took 0.5331928730010986s
Currency | Modification date check for Bio2RDF::Interpro took 0.5169234275817871s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 108.22176504135132s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 11.741934776306152s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.43453073501586914s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.28681039810180664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2734968662261963s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 6.949274063110352s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8976523876190186s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6805477142333984s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.4159848690032959s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.3055009841919s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.3664002418518066s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 7.021191596984863s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.343224048614502s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.56899380683899s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.716195821762085s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.4245128631591797s
Security | Sign check for Bio2RDF::Interpro took 0.2696213722229004s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 12.412681341171265s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.8241157531738281s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.0325617790222168s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010514259338378906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 12.639060735702515s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-interpro took 1030.7450921535492s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.1391305923461914s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.7101249694824219s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.581710815429688e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-iproclass took 18.41579508781433s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.46970033645629883s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006012916564941406s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 19.078963041305542s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.268354892730713s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 44.13889122009277s
Interoperability | New terms check for Bio2RDF::Irefindex took 41.58542728424072s
Versatility | Languages check for Bio2RDF::Irefindex took 60.264729261398315s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2773616313934326s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15790843963623047s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.37933778762817383s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3185617923736572s
Availability | RDF dump link check for Bio2RDF::Irefindex took 0.3021225929260254s
License | MR license check for Bio2RDF::Irefindex took 0.5057768821716309s
License | HR license check for Bio2RDF::Irefindex took 60.264047145843506s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2567784786224365s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.19329023361206s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.582603931427002s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2656819820404053s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2423999309539795s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2670876979827881s
Performance | Throughput check for Bio2RDF::Irefindex took 11.62652325630188s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 77.36578822135925s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6042532920837402s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.34853386878967285s
Interlinking | skos check for Bio2RDF::Irefindex took 0.7356104850769043s
Interlinking | skos check for Bio2RDF::Irefindex took 0.35142946243286133s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.26433396339416504s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5137820243835449s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5178461074829102s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 110.17058992385864s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 14.945111513137817s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.39421916007995605s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.252673864364624s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.2792854309082031s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 6.487371921539307s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.9099225997924805s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.7156462669372559s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.44833803176879883s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.36310029029846s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.4780025482177734s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.401742696762085s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3239154815673828s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.57340598106384s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7087550163269043s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.42801761627197266s
Security | Sign check for Bio2RDF::Irefindex took 0.2815103530883789s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 11.513682126998901s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 1.4781641960144043s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.021004915237426758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 6.437301635742188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 12.76540994644165s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1053.1680674552917s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.2527744770050049s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.198883056640625e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-kegg took 3.7931180000305176s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.68918776512146s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02055811882019043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.8457298278808594s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13874268531799316s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2579805850982666s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.02095961570739746s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 9.47088360786438s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.4890139102935791s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006351470947265625s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.219952821731567s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.248906135559082s
Amount of data | Number of triples check for Bio2RDF::Lsr took 45.50154995918274s
Interoperability | New terms check for Bio2RDF::Lsr took 40.846728801727295s
Versatility | Languages check for Bio2RDF::Lsr took 60.25503182411194s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.26914501190185547s
Security | Check HTTPS for Bio2RDF::Lsr took 0.16756272315979004s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.9090671539306641s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3119339942932129s
Availability | RDF dump link check for Bio2RDF::Lsr took 0.30317211151123047s
License | MR license check for Bio2RDF::Lsr took 0.45717763900756836s
License | HR license check for Bio2RDF::Lsr took 60.26815676689148s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.24233365058898926s
Understandability | Number of label check for Bio2RDF::Lsr took 9.640125513076782s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5913443565368652s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.25258302688598633s
Verifiability | Authors check for Bio2RDF::Lsr took 0.28104305267333984s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.26279377937316895s
Performance | Throughput check for Bio2RDF::Lsr took 11.45249056816101s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 76.44340300559998s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.7484467029571533s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3667268753051758s
Interlinking | skos check for Bio2RDF::Lsr took 0.8968024253845215s
Interlinking | skos check for Bio2RDF::Lsr took 0.35204029083251953s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.2746758460998535s
Currency | Creation date check for Bio2RDF::Lsr took 0.5115711688995361s
Currency | Modification date check for Bio2RDF::Lsr took 0.5222768783569336s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 109.32477474212646s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 12.504886388778687s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.41780734062194824s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.276003360748291s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2506406307220459s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.060532808303833s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.9068646430969238s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.7156460285186768s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.42000651359558105s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.17297124862671s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.437229871749878s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.510866641998291s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3776295185089111s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.623924255371094s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7288467884063721s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.4226698875427246s
Security | Sign check for Bio2RDF::Lsr took 0.26485323905944824s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 12.435332536697388s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.44917917251586914s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02076244354248047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 13.215420961380005s
Believability | Calculation of trust value for Bio2RDF::Lsr took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-lsr took 1030.5448698997498s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.4709484577178955s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0005860328674316406s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.4132297039032s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2416415214538574s
Amount of data | Number of triples check for Bio2RDF::Mesh took 43.559749603271484s
Interoperability | New terms check for Bio2RDF::Mesh took 40.7913384437561s
Versatility | Languages check for Bio2RDF::Mesh took 60.23648452758789s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.28347229957580566s
Security | Check HTTPS for Bio2RDF::Mesh took 0.16575098037719727s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.5492880344390869s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.3129723072052002s
Availability | RDF dump link check for Bio2RDF::Mesh took 0.30025291442871094s
License | MR license check for Bio2RDF::Mesh took 0.5603430271148682s
License | HR license check for Bio2RDF::Mesh took 60.245813846588135s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2660517692565918s
Understandability | Number of label check for Bio2RDF::Mesh took 9.572369813919067s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5829510688781738s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.26873159408569336s
Verifiability | Authors check for Bio2RDF::Mesh took 0.25433993339538574s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.27437877655029297s
Performance | Throughput check for Bio2RDF::Mesh took 11.198493242263794s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 73.25832843780518s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.5710079669952393s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.3541374206542969s
Interlinking | skos check for Bio2RDF::Mesh took 0.7502322196960449s
Interlinking | skos check for Bio2RDF::Mesh took 0.3482961654663086s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.25882577896118164s
Currency | Creation date check for Bio2RDF::Mesh took 0.503148078918457s
Currency | Modification date check for Bio2RDF::Mesh took 0.5183873176574707s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 107.6861789226532s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 12.438518524169922s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.40827250480651855s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2825150489807129s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2850644588470459s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.36809229850769s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8980655670166016s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6791448593139648s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.28760480880737305s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.42403388023376s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.4172232151031494s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.510457754135132s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3103158473968506s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.59353280067444s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.717829704284668s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.43062591552734375s
Security | Sign check for Bio2RDF::Mesh took 0.2745389938354492s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 12.42427945137024s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 1.3531789779663086s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.843971252441406e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 12.041818857192993s
Believability | Calculation of trust value for Bio2RDF::Mesh took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-mesh took 1026.6896421909332s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 1.2947502136230469s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006053447723388672s
Extra | Recovery of all triples for Bio2RDF::Mgi took 18.075223922729492s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2286248207092285s
Amount of data | Number of triples check for Bio2RDF::Mgi took 44.15760636329651s
Interoperability | New terms check for Bio2RDF::Mgi took 43.581756353378296s
Versatility | Languages check for Bio2RDF::Mgi took 60.24514985084534s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.2825288772583008s
Security | Check HTTPS for Bio2RDF::Mgi took 0.14722108840942383s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.48224663734436035s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.32114505767822266s
Availability | RDF dump link check for Bio2RDF::Mgi took 0.2880513668060303s
License | MR license check for Bio2RDF::Mgi took 0.6201052665710449s
License | HR license check for Bio2RDF::Mgi took 60.2420334815979s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.26877784729003906s
Understandability | Number of label check for Bio2RDF::Mgi took 9.698470830917358s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5859951972961426s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2483055591583252s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2641119956970215s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2794482707977295s
Performance | Throughput check for Bio2RDF::Mgi took 10.990925550460815s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 75.81892395019531s
Verifiability | Contribs. check for Bio2RDF::Mgi took 2.054877281188965s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.34764933586120605s
Interlinking | skos check for Bio2RDF::Mgi took 0.7242755889892578s
Interlinking | skos check for Bio2RDF::Mgi took 0.3636205196380615s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.26842832565307617s
Currency | Creation date check for Bio2RDF::Mgi took 0.5248150825500488s
Currency | Modification date check for Bio2RDF::Mgi took 0.49662280082702637s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 109.72096490859985s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 12.334297895431519s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.436870813369751s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.27854275703430176s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.26210689544677734s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.243745565414429s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.9205992221832275s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6764209270477295s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.36823081970214844s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.63779544830322s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4183568954467773s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 5.8745527267456055s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3287694454193115s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.574626207351685s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7072384357452393s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.42993593215942383s
Security | Sign check for Bio2RDF::Mgi took 0.28806185722351074s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 12.486786365509033s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.42865991592407227s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02055811882019043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.369850158691406e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 26.64246153831482s
Believability | Calculation of trust value for Bio2RDF::Mgi took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-mgi took 1050.4951481819153s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.4780416488647461s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.00077056884765625s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 21.55509352684021s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.3081438541412354s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 44.44451022148132s
Interoperability | New terms check for Bio2RDF::Ncbigene took 43.87561798095703s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.25119614601135s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2733955383300781s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.14490962028503418s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.9353525638580322s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.33202624320983887s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 0.29178309440612793s
License | MR license check for Bio2RDF::Ncbigene took 0.5045521259307861s
License | HR license check for Bio2RDF::Ncbigene took 60.23893475532532s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2656059265136719s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.358232498168945s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.6033403873443604s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.2594640254974365s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2713034152984619s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.25049448013305664s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.038885593414307s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 76.15894079208374s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.9517090320587158s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.33133983612060547s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.9501566886901855s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.33489084243774414s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.25549983978271484s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5113277435302734s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.4994161128997803s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 110.01931095123291s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 17.203131914138794s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4215662479400635s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2703256607055664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.26184868812561035s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.599398136138916s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.916405439376831s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6584887504577637s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.36972713470458984s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.95934343338013s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.432042121887207s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.651121139526367s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3647434711456299s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.56542634963989s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7156417369842529s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.4663879871368408s
Security | Sign check for Bio2RDF::Ncbigene took 0.2749664783477783s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 12.023754596710205s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.5061109066009521s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012612342834472656s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 12.18922209739685s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1047.8018171787262s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.460371732711792s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006220340728759766s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.55308747291565s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2457497119903564s
Amount of data | Number of triples check for Bio2RDF::Ndc took 44.111449003219604s
Interoperability | New terms check for Bio2RDF::Ndc took 42.7486469745636s
Versatility | Languages check for Bio2RDF::Ndc took 60.246325969696045s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2550220489501953s
Security | Check HTTPS for Bio2RDF::Ndc took 0.16457557678222656s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.9737069606781006s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.3214681148529053s
Availability | RDF dump link check for Bio2RDF::Ndc took 0.2905547618865967s
License | MR license check for Bio2RDF::Ndc took 0.49583911895751953s
License | HR license check for Bio2RDF::Ndc took 60.239336013793945s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2697181701660156s
Understandability | Number of label check for Bio2RDF::Ndc took 9.898360967636108s
Understandability | URI regex check for Bio2RDF::Ndc took 0.6000347137451172s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.25592613220214844s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2690393924713135s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.27173566818237305s
Performance | Throughput check for Bio2RDF::Ndc took 11.291585206985474s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 80.5702645778656s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.7560710906982422s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.39130544662475586s
Interlinking | skos check for Bio2RDF::Ndc took 0.8854100704193115s
Interlinking | skos check for Bio2RDF::Ndc took 0.3625333309173584s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.27112293243408203s
Currency | Creation date check for Bio2RDF::Ndc took 0.5356898307800293s
Currency | Modification date check for Bio2RDF::Ndc took 0.5397474765777588s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 108.27798914909363s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 12.392596960067749s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.42768287658691406s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2626657485961914s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2643880844116211s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.4621806144714355s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.9195542335510254s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6766364574432373s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.4391481876373291s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 66.027104139328s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4603137969970703s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.836233854293823s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3607463836669922s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.5551700592041s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7184104919433594s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.45117688179016113s
Security | Sign check for Bio2RDF::Ndc took 0.26244616508483887s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 12.497678756713867s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 1.41151762008667s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 18.46339726448059s
Believability | Calculation of trust value for Bio2RDF::Ndc took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-ndc took 1043.509874343872s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 5.555152893066406e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.7013051509857178s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-netpath took 5.574511289596558s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.1307051181793213s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2667381763458252s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-nextprot took 3.342139959335327s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.4786539077758789s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006582736968994141s
Extra | Recovery of all triples for Bio2RDF::Omim took 19.023873805999756s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.251110315322876s
Amount of data | Number of triples check for Bio2RDF::Omim took 45.05337476730347s
Interoperability | New terms check for Bio2RDF::Omim took 41.60486173629761s
Versatility | Languages check for Bio2RDF::Omim took 60.246647357940674s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2743508815765381s
Security | Check HTTPS for Bio2RDF::Omim took 0.156571626663208s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.5353114604949951s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.30254507064819336s
Availability | RDF dump link check for Bio2RDF::Omim took 0.30284643173217773s
License | MR license check for Bio2RDF::Omim took 0.4945333003997803s
License | HR license check for Bio2RDF::Omim took 60.23878288269043s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2513582706451416s
Understandability | Number of label check for Bio2RDF::Omim took 9.811382293701172s
Understandability | URI regex check for Bio2RDF::Omim took 0.6034848690032959s
Understandability | Vocabs check for Bio2RDF::Omim took 0.26009464263916016s
Verifiability | Authors check for Bio2RDF::Omim took 0.26252174377441406s
Verifiability | Publishers check for Bio2RDF::Omim took 0.25629162788391113s
Performance | Throughput check for Bio2RDF::Omim took 10.795679807662964s
Amount of data | Check the number of entities for Bio2RDF::Omim took 75.58586740493774s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.6039133071899414s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.36971497535705566s
Interlinking | skos check for Bio2RDF::Omim took 0.8782181739807129s
Interlinking | skos check for Bio2RDF::Omim took 0.3422579765319824s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.27441883087158203s
Currency | Creation date check for Bio2RDF::Omim took 0.5331761837005615s
Currency | Modification date check for Bio2RDF::Omim took 0.515373945236206s
Rep.Conc. | URIs length for Bio2RDF::Omim took 109.27782702445984s
Interoperability | New vocabularies check for Bio2RDF::Omim took 13.145320653915405s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.42931461334228516s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2892038822174072s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.26369643211364746s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.23613715171814s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.9006457328796387s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6897127628326416s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.4208040237426758s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.1293158531189s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.403219223022461s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.174115180969238s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3669512271881104s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.57373547554016s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7203936576843262s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.4203643798828125s
Security | Sign check for Bio2RDF::Omim took 0.25879645347595215s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 11.684314966201782s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.9100916385650635s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02101898193359375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013303756713867188s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 11.7476646900177s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-omim took 1032.460896730423s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.863739013671875e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.7188522815704346s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.0200197696685791s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.933906555175781e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 3.9799909591674805s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.467052698135376s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0006737709045410156s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 19.325655460357666s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2618896961212158s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 43.39654064178467s
Interoperability | New terms check for Bio2RDF::Orphanet took 41.597445487976074s
Versatility | Languages check for Bio2RDF::Orphanet took 60.24274206161499s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.27420592308044434s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.16438078880310059s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.8934576511383057s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.30224609375s
Availability | RDF dump link check for Bio2RDF::Orphanet took 0.289794921875s
License | MR license check for Bio2RDF::Orphanet took 0.4951817989349365s
License | HR license check for Bio2RDF::Orphanet took 60.25586986541748s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.28576040267944336s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.528217077255249s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5813961029052734s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.25092506408691406s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.26810288429260254s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2682075500488281s
Performance | Throughput check for Bio2RDF::Orphanet took 11.912832021713257s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 76.16958379745483s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.5987255573272705s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.32909154891967773s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7413971424102783s
Interlinking | skos check for Bio2RDF::Orphanet took 0.33249616622924805s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.25150442123413086s
Currency | Creation date check for Bio2RDF::Orphanet took 0.526160717010498s
Currency | Modification date check for Bio2RDF::Orphanet took 0.4781005382537842s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 108.31417417526245s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 12.260852336883545s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4212820529937744s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2957460880279541s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2808494567871094s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 7.907432556152344s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.9089035987854004s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6726517677307129s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.46145129203796387s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 64.85254859924316s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.405196189880371s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.119600772857666s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3120112419128418s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.54916429519653s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7051002979278564s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.4512801170349121s
Security | Sign check for Bio2RDF::Orphanet took 0.27155590057373047s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 12.573368549346924s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.40935349464416504s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.021322965621948242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0009801387786865234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.535385131835938e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 12.027567863464355s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1035.1222817897797s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.13068389892578125s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.2507815361022949s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 10.315035820007324s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.4776144027709961s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005598068237304688s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.060784578323364s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2374930381774902s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 43.41528797149658s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 41.75523614883423s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.25528025627136s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2575092315673828s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.16611504554748535s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.7641773223876953s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.30602526664733887s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 0.29581284523010254s
License | MR license check for Bio2RDF::Pharmgkb took 0.5202109813690186s
License | HR license check for Bio2RDF::Pharmgkb took 60.250216007232666s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2583603858947754s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.99517035484314s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5918688774108887s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2651052474975586s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2920873165130615s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.278606653213501s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.108622550964355s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 75.90371012687683s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.6024391651153564s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.36061906814575195s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.8146984577178955s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.33148717880249023s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.26404595375061035s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5207855701446533s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5175707340240479s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 107.92141890525818s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 13.015289545059204s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.40169739723205566s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2701256275177002s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.27956080436706543s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.910353422164917s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.9255502223968506s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6750173568725586s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4085853099822998s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 64.94104599952698s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.433701992034912s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.706219911575317s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3301174640655518s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.57658910751343s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7003281116485596s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4453718662261963s
Security | Sign check for Bio2RDF::Pharmgkb took 0.28041601181030273s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 12.172762632369995s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.3765685558319092s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 0.00013518333435058594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 12.530425786972046s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1035.0379769802094s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 0.000118255615234375s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.7011072635650635s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.252603769302368s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 9.274482727050781e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0003325939178466797s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.7246994972229004s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-pid took 3.824275255203247s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.2507944107055664s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.334110975265503s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.47455453872680664s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0007596015930175781s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.57511854171753s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2813003063201904s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 43.4739933013916s
Interoperability | New terms check for Bio2RDF::Pubmed took 43.41980457305908s
Versatility | Languages check for Bio2RDF::Pubmed took 60.24629187583923s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.25516772270202637s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.15437531471252441s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.5560963153839111s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.298168420791626s
Availability | RDF dump link check for Bio2RDF::Pubmed took 0.2930877208709717s
License | MR license check for Bio2RDF::Pubmed took 0.4198179244995117s
License | HR license check for Bio2RDF::Pubmed took 60.23482036590576s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.25577521324157715s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.700171947479248s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6129288673400879s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2717106342315674s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.26657891273498535s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.2606472969055176s
Performance | Throughput check for Bio2RDF::Pubmed took 11.235212326049805s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 77.95392060279846s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.5929162502288818s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.4101293087005615s
Interlinking | skos check for Bio2RDF::Pubmed took 1.2400012016296387s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3467068672180176s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2776491641998291s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5267951488494873s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5028185844421387s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 109.3988254070282s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 12.470612049102783s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.4476468563079834s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.27091097831726074s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.27348899841308594s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.554258584976196s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.9130744934082031s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6751797199249268s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.36927294731140137s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.26727223396301s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.4238505363464355s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.57307767868042s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3572440147399902s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.56398057937622s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7098362445831299s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.42133212089538574s
Security | Sign check for Bio2RDF::Pubmed took 0.27684640884399414s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 12.402766942977905s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.5387945175170898s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.021054506301879883s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001342296600341797s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 11.683918476104736s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1034.7452139854431s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 0.00010347366333007812s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.27902984619140625s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020236730575561523s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.985664367675781e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-reactome took 4.226359844207764s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 5.221366882324219e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.26270246505737305s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.435943603515625e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.369142770767212s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1301579475402832s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.26933956146240234s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.581710815429688e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sabiork took 8.599850416183472s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.47039318084716797s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0007293224334716797s
Extra | Recovery of all triples for Bio2RDF::Sgd took 20.263548851013184s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2435498237609863s
Amount of data | Number of triples check for Bio2RDF::Sgd took 43.83305239677429s
Interoperability | New terms check for Bio2RDF::Sgd took 41.57357835769653s
Versatility | Languages check for Bio2RDF::Sgd took 60.24051570892334s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.24492573738098145s
Security | Check HTTPS for Bio2RDF::Sgd took 0.16562819480895996s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.7511675357818604s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.3406996726989746s
Availability | RDF dump link check for Bio2RDF::Sgd took 0.2879033088684082s
License | MR license check for Bio2RDF::Sgd took 0.48003363609313965s
License | HR license check for Bio2RDF::Sgd took 60.249269247055054s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.26571083068847656s
Understandability | Number of label check for Bio2RDF::Sgd took 10.003219842910767s
Understandability | URI regex check for Bio2RDF::Sgd took 0.6010973453521729s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2639150619506836s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2744176387786865s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.28496837615966797s
Performance | Throughput check for Bio2RDF::Sgd took 11.232211351394653s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 77.20125889778137s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.5763988494873047s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.35169196128845215s
Interlinking | skos check for Bio2RDF::Sgd took 0.9725837707519531s
Interlinking | skos check for Bio2RDF::Sgd took 0.3495364189147949s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.273118257522583s
Currency | Creation date check for Bio2RDF::Sgd took 0.5064311027526855s
Currency | Modification date check for Bio2RDF::Sgd took 0.516167402267456s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 112.64924550056458s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 11.546813249588013s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.4304325580596924s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2702648639678955s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.26529836654663086s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 7.480403423309326s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.9189155101776123s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6750245094299316s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.3908350467681885s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.13757872581482s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4160513877868652s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.377352237701416s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3445651531219482s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.59493851661682s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7122442722320557s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.406543493270874s
Security | Sign check for Bio2RDF::Sgd took 0.29233622550964355s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 12.245991468429565s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.9654810428619385s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011682510375976562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 12.033672332763672s
Believability | Calculation of trust value for Bio2RDF::Sgd took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-sgd took 1032.9761943817139s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.4345855712890625e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.701479434967041s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 4.363059997558594e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 4.5118372440338135s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 1.2705028057098389s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006382465362548828s
Extra | Recovery of all triples for Bio2RDF::Sider took 23.292646646499634s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.3062875270843506s
Amount of data | Number of triples check for Bio2RDF::Sider took 44.94477462768555s
Interoperability | New terms check for Bio2RDF::Sider took 42.45132851600647s
Versatility | Languages check for Bio2RDF::Sider took 60.228801250457764s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.27470993995666504s
Security | Check HTTPS for Bio2RDF::Sider took 0.16709113121032715s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.628291130065918s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.32000017166137695s
Availability | RDF dump link check for Bio2RDF::Sider took 0.3054671287536621s
License | MR license check for Bio2RDF::Sider took 0.5010213851928711s
License | HR license check for Bio2RDF::Sider took 60.24378967285156s
Amount of data | Number of property check for Bio2RDF::Sider took 0.28681325912475586s
Understandability | Number of label check for Bio2RDF::Sider took 9.623968362808228s
Understandability | URI regex check for Bio2RDF::Sider took 0.5802721977233887s
Understandability | Vocabs check for Bio2RDF::Sider took 0.27927446365356445s
Verifiability | Authors check for Bio2RDF::Sider took 0.2757432460784912s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2668604850769043s
Performance | Throughput check for Bio2RDF::Sider took 11.20334267616272s
Amount of data | Check the number of entities for Bio2RDF::Sider took 76.80508327484131s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.5820446014404297s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3428471088409424s
Interlinking | skos check for Bio2RDF::Sider took 0.7394182682037354s
Interlinking | skos check for Bio2RDF::Sider took 0.3510754108428955s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.27822208404541016s
Currency | Creation date check for Bio2RDF::Sider took 0.5317981243133545s
Currency | Modification date check for Bio2RDF::Sider took 0.517686128616333s
Rep.Conc. | URIs length for Bio2RDF::Sider took 108.9236581325531s
Interoperability | New vocabularies check for Bio2RDF::Sider took 13.050951957702637s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.40590834617614746s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.26251912117004395s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2597634792327881s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.039641618728638s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8990681171417236s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6639292240142822s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.4254128932952881s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.19939184188843s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.4023401737213135s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.792121410369873s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3279213905334473s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.570237159729004s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.703742265701294s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.41171860694885254s
Security | Sign check for Bio2RDF::Sider took 0.26295995712280273s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 11.293261766433716s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.33469223976135254s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.021060705184936523s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 11.79450011253357s
Believability | Calculation of trust value for Bio2RDF::Sider took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-sider took 1038.375462770462s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.25516319274902344s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020296335220336914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-spike took 3.786994218826294s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.3392181396484375e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.7070393562316895s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.021416902542114258s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0009341239929199219s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 5.173683166503906e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-taxon took 3.5550355911254883s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.4579789638519287s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0003159046173095703s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.44174027442932s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2538940906524658s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 43.57831358909607s
Interoperability | New terms check for Bio2RDF::Taxonomy took 41.35559010505676s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.236135482788086s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2753009796142578s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.1725630760192871s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.6367013454437256s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.32753920555114746s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 0.291301965713501s
License | MR license check for Bio2RDF::Taxonomy took 0.3745448589324951s
License | HR license check for Bio2RDF::Taxonomy took 60.25427508354187s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2565116882324219s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.9375638961792s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6120672225952148s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.25751709938049316s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.26975560188293457s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.23777198791503906s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.683317184448242s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 74.4931902885437s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.589491605758667s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.36397314071655273s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.7457408905029297s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.3574371337890625s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2804265022277832s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.4872269630432129s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5247068405151367s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 108.95860433578491s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 12.185291528701782s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4164886474609375s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2643718719482422s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.284527063369751s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 7.765178918838501s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.9069235324859619s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.709087610244751s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.4021165370941162s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.07007908821106s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.4529783725738525s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.273994445800781s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3318190574645996s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.58436417579651s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7164051532745361s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.42577362060546875s
Security | Sign check for Bio2RDF::Taxonomy took 0.2662789821624756s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 11.310251951217651s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.9726057052612305s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.021697282791137695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 6.508827209472656e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010061264038085938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 11.7355637550354s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1028.145606994629s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.13574862480163574s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.7085013389587402s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020210742950439453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 18.51315426826477s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4816434383392334s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006444454193115234s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 19.639777898788452s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.1744194030761719s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 43.70168423652649s
Interoperability | New terms check for Bio2RDF::Wormbase took 42.5994610786438s
Versatility | Languages check for Bio2RDF::Wormbase took 60.23893117904663s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.28795647621154785s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15745139122009277s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.6133959293365479s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3482530117034912s
Availability | RDF dump link check for Bio2RDF::Wormbase took 0.3022651672363281s
License | MR license check for Bio2RDF::Wormbase took 0.4244399070739746s
License | HR license check for Bio2RDF::Wormbase took 60.25035333633423s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.27513766288757324s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.074522495269775s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6229591369628906s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2550392150878906s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2671835422515869s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.26457762718200684s
Performance | Throughput check for Bio2RDF::Wormbase took 11.01533055305481s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 76.42666506767273s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.7767338752746582s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.35703468322753906s
Interlinking | skos check for Bio2RDF::Wormbase took 0.7778575420379639s
Interlinking | skos check for Bio2RDF::Wormbase took 0.34644436836242676s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.27007365226745605s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5337631702423096s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5165426731109619s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 110.59065747261047s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 17.64783501625061s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4071669578552246s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.26439523696899414s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.26252007484436035s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.819478511810303s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.9063034057617188s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.656853437423706s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.3990497589111328s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.227783203125s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.431715726852417s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.4629807472229s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3474805355072021s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.55498552322388s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7055013179779053s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.43184733390808105s
Security | Sign check for Bio2RDF::Wormbase took 0.27599644660949707s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 11.258803606033325s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.986281156539917s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.130073547363281e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 12.965677976608276s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1043.7925357818604s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.2443985939025879s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.26937031745910645s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.320808410644531e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 5.7220458984375e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.5083303451538086s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.1484832763671875e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.29484081268310547s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.9802322387695312e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for biolit took 3.246687412261963s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6488523483276367s
Availability | VoID file availability check for BioModels RDF took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.27376341819763184s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020246505737304688s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for BioModels RDF took 7.3909759521484375e-06s
INFO | --- Analysis for biomodels-rdf took 4.13291597366333s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2657485008239746s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.021158933639526367s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006470680236816406s
Believability | Calculation of trust value for Amphibian gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-aao took 6.382326126098633s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.38690185546875e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.3248913288116455s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00031685829162597656s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-aba took 5.775962829589844s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.982948303222656e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2860710620880127s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020813941955566406s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015730857849121094s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-acgt took 4.169580698013306s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.291534423828125e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.26407957077026367s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003306865692138672s
Believability | Calculation of trust value for Animal natural history and life history took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-adw took 3.8070318698883057s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.26990342140197754s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00046181678771972656s
Believability | Calculation of trust value for Anatomical Entity Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-aeo took 3.899075746536255s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 5.507469177246094e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.25551557540893555s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009853839874267578s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-aero took 3.966543436050415s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.410743713378906e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2619948387145996s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020274639129638672s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004050731658935547s
Believability | Calculation of trust value for AI/RHEUM took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-air took 4.060122489929199s
Availability | SPARQL endpoint availability check for Amino Acid took 4.6253204345703125e-05s
Availability | VoID file availability check for Amino Acid took 0.00033855438232421875s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.2696418762207031s
Reputation | Calculation of the PageRank for Amino Acid took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Amino Acid took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00025177001953125s
Believability | Calculation of trust value for Amino Acid took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-amino-acid took 4.4789719581604s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 5.555152893066406e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.27950358390808105s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002906322479248047s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-apo took 3.908350944519043s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.220008850097656e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2567164897918701s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00023818016052246094s
Believability | Calculation of trust value for African Traditional Medicine took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-atmo took 3.904808521270752s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.410743713378906e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2704811096191406s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.726119995117188e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ato took 3.971552610397339s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2948777675628662s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020342111587524414s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013382434844970703s
Believability | Calculation of trust value for BioAssay Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bao took 3.8931005001068115s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.315376281738281e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.27316761016845703s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00039076805114746094s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 3.9778692722320557s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2606518268585205s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003292560577392578s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bcgo took 3.901965856552124s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.000762939453125s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.2672908306121826s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.00140380859375s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bdo took 3.8215060234069824s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.24884867668151855s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.02186298370361328s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0010712146759033203s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005819797515869141s
Believability | Calculation of trust value for Basic Formal Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bfo took 4.06915283203125s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.363059997558594e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.24474191665649414s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007472038269042969s
Believability | Calculation of trust value for Bleeding History Phenotype took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bho took 3.8741233348846436s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.26262950897216797s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00045299530029296875s
Believability | Calculation of trust value for Bilateria anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bila took 3.9622604846954346s
Availability | SPARQL endpoint availability check for BIRNLex took 4.3392181396484375e-05s
Availability | VoID file availability check for BIRNLex took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.27274370193481445s
Reputation | Calculation of the PageRank for BIRNLex took 0.02090167999267578s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0015435218811035156s
Believability | Calculation of trust value for BIRNLex took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-birnlex took 4.968868017196655s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.27699971199035645s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007421970367431641s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bootstrep took 5.255760431289673s
Availability | SPARQL endpoint availability check for BioPAX took 4.2438507080078125e-05s
Availability | VoID file availability check for BioPAX took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for BioPAX took 0.25668978691101074s
Reputation | Calculation of the PageRank for BioPAX took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for BioPAX took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.512901306152344e-05s
Believability | Calculation of trust value for BioPAX took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bp took 4.299672603607178s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2773904800415039s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.02064657211303711s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003376007080078125s
Believability | Calculation of trust value for Biomedical Resource Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 4.298367500305176s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.25743627548217773s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020701885223388672s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00021910667419433594s
Believability | Calculation of trust value for Spatial Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-bspo took 4.0725109577178955s
Availability | SPARQL endpoint availability check for BioTop took 4.2438507080078125e-05s
Availability | VoID file availability check for BioTop took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for BioTop took 0.25948214530944824s
Reputation | Calculation of the PageRank for BioTop took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for BioTop took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006687641143798828s
Believability | Calculation of trust value for BioTop took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bt took 3.9504618644714355s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.410743713378906e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.2568836212158203s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008957386016845703s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bto took 3.8555614948272705s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.30805349349975586s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018694400787353516s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-canco took 4.271428823471069s
Availability | SPARQL endpoint availability check for CAO took 5.078315734863281e-05s
Availability | VoID file availability check for CAO took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for CAO took 0.2651517391204834s
Reputation | Calculation of the PageRank for CAO took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for CAO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005981922149658203s
Believability | Calculation of trust value for CAO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cao took 4.183928489685059s
Availability | SPARQL endpoint availability check for CareLex took 4.410743713378906e-05s
Availability | VoID file availability check for CareLex took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for CareLex took 0.2422018051147461s
Reputation | Calculation of the PageRank for CareLex took 0.020841598510742188s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.9114227294921875e-05s
Believability | Calculation of trust value for CareLex took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-carelex took 3.716466188430786s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 9.965896606445312e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2835695743560791s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008056163787841797s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cco took 3.9131548404693604s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.25207972526550293s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002562999725341797s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cdao took 4.181511163711548s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.649162292480469e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2720355987548828s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020856142044067383s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0008199214935302734s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008847713470458984s
Believability | Calculation of trust value for Chemical entities of biological interest took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-chebi took 3.953249454498291s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.744529724121094e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.24848699569702148s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002532005310058594s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 4.0226733684539795s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.26831626892089844s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007731914520263672s
Believability | Calculation of trust value for Chemical Information Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-cheminf took 3.9470269680023193s
Availability | SPARQL endpoint availability check for Cell type took 4.315376281738281e-05s
Availability | VoID file availability check for Cell type took 0.0003104209899902344s
Completeness | Calculation of interlinking completeness for Cell type took 0.2573831081390381s
Reputation | Calculation of the PageRank for Cell type took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003802776336669922s
Believability | Calculation of trust value for Cell type took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cl took 3.842114210128784s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0003521442413330078s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.25983524322509766s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020356178283691406s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008075237274169922s
Believability | Calculation of trust value for Cell Line Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-clo took 3.8783199787139893s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0003452301025390625s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2513720989227295s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017118453979492188s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cmo took 3.8337016105651855s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.25243377685546875s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02028965950012207s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002052783966064453s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cno took 3.8616631031036377s
Availability | SPARQL endpoint availability check for Wheat trait took 8.463859558105469e-05s
Availability | VoID file availability check for Wheat trait took 0.0008308887481689453s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.27959609031677246s
Reputation | Calculation of the PageRank for Wheat trait took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Wheat trait took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.221366882324219e-05s
Believability | Calculation of trust value for Wheat trait took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-co_wheat took 4.138376951217651s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.2438507080078125e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.25953221321105957s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.000347137451171875s
Believability | Calculation of trust value for Cognitive Atlas took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-cogat took 3.8308277130126953s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.25610852241516113s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.02085089683532715s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007631778717041016s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-cogpo took 3.9218194484710693s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.4345855712890625e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0007560253143310547s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.25896406173706055s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.021092653274536133s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0008797645568847656s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004849433898925781s
Believability | Calculation of trust value for Current Procedural Terminology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cpt took 3.9654083251953125s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.38690185546875e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.000732421875s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.31678342819213867s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0018036365509033203s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-csp took 4.35677170753479s
Availability | SPARQL endpoint availability check for COSTART took 4.38690185546875e-05s
Availability | VoID file availability check for COSTART took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for COSTART took 0.2631845474243164s
Reputation | Calculation of the PageRank for COSTART took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009958744049072266s
Believability | Calculation of trust value for COSTART took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cst took 4.208291530609131s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.410743713378906e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.28124332427978516s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004923343658447266s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ctcae took 3.9552297592163086s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.38690185546875e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2718207836151123s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020994186401367188s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0008087158203125s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004756450653076172s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ctx took 3.791422128677368s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.220008850097656e-05s
Availability | VoID file availability check for Dendritic cell took 0.0003447532653808594s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2360241413116455s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00029087066650390625s
Believability | Calculation of trust value for Dendritic cell took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-dc_cl took 3.8527512550354004s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.5299530029296875e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2598717212677002s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0008311271667480469s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.322166442871094e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ddanat took 3.8413572311401367s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0003612041473388672s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2526233196258545s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009675025939941406s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ddi took 4.155332326889038s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.26467108726501465s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.0207064151763916s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 9.036064147949219e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-diagnosticont took 5.155432939529419s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2571408748626709s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001704692840576172s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 3.9463250637054443s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Human disease ontology took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2789323329925537s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006501674652099609s
Believability | Calculation of trust value for Human disease ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-doid took 4.432345390319824s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0007746219635009766s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2790837287902832s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008053779602050781s
Believability | Calculation of trust value for Electrocardiography Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ecg took 3.7924575805664062s
Availability | SPARQL endpoint availability check for Evidence codes took 4.291534423828125e-05s
Availability | VoID file availability check for Evidence codes took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2618863582611084s
Reputation | Calculation of the PageRank for Evidence codes took 0.020995140075683594s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0009083747863769531s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.337860107421875e-05s
Believability | Calculation of trust value for Evidence codes took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-eco took 3.8919172286987305s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.00034165382385253906s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.28006649017333984s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017228126525878906s
Believability | Calculation of trust value for Experimental Factor Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-efo took 4.287734031677246s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.315376281738281e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0003726482391357422s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.25374507904052734s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0009071826934814453s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.00125885009765625s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehda took 3.756976842880249s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.315376281738281e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.000377655029296875s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.2536604404449463s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007250308990478516s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ehdaa took 4.047501564025879s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.363059997558594e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0003428459167480469s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.25982165336608887s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005204677581787109s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 3.9583168029785156s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.3392181396484375e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.24673700332641602s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.170967102050781e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-emap took 3.7141809463500977s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Environment Ontology took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2892887592315674s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0004012584686279297s
Believability | Calculation of trust value for Environment Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-envo took 3.941185474395752s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.291534423828125e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.26358485221862793s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00030159950256347656s
Believability | Calculation of trust value for Plant environmental conditions took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-eo took 4.1028687953948975s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0008192062377929688s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.24382829666137695s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02037668228149414s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012354850769042969s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ep took 3.992192268371582s
Availability | SPARQL endpoint availability check for Epilepsy took 4.315376281738281e-05s
Availability | VoID file availability check for Epilepsy took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2597160339355469s
Reputation | Calculation of the PageRank for Epilepsy took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Epilepsy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001304149627685547s
Believability | Calculation of trust value for Epilepsy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-epileponto took 4.1809046268463135s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.363059997558594e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2534513473510742s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.001163482666015625s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ero took 4.0369133949279785s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.291534423828125e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.26763296127319336s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011212825775146484s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ev took 4.155003070831299s
Availability | SPARQL endpoint availability check for ExO took 6.747245788574219e-05s
Availability | VoID file availability check for ExO took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for ExO took 0.2786879539489746s
Reputation | Calculation of the PageRank for ExO took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for ExO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00024127960205078125s
Believability | Calculation of trust value for ExO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-exo took 4.0248143672943115s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.744529724121094e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.23887872695922852s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011873245239257812s
Believability | Calculation of trust value for Fungal gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fao took 3.9492404460906982s
Availability | SPARQL endpoint availability check for Biological imaging methods took 7.104873657226562e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0008151531219482422s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.27950406074523926s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.02070307731628418s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00021505355834960938s
Believability | Calculation of trust value for Biological imaging methods took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbbi took 4.126615285873413s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.26868724822998047s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006506443023681641s
Believability | Calculation of trust value for Drosophila gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbbt took 3.8652453422546387s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 7.033348083496094e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.282245397567749s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00042700767517089844s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-fbcv took 5.627952337265015s
Availability | SPARQL endpoint availability check for Drosophila development took 4.38690185546875e-05s
Availability | VoID file availability check for Drosophila development took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2465527057647705s
Reputation | Calculation of the PageRank for Drosophila development took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.410743713378906e-05s
Believability | Calculation of trust value for Drosophila development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fbdv took 3.919924736022949s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.26807355880737305s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.00038123130798339844s
Believability | Calculation of trust value for Fly taxonomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbsp took 3.8204009532928467s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.363059997558594e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.28372955322265625s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00023794174194335938s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 4.10368275642395s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.25617194175720215s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004260540008544922s
Believability | Calculation of trust value for Family Health History Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-fhho took 3.8264636993408203s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.32389307022094727s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.000997304916381836s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001226186752319336s
Believability | Calculation of trust value for Influenza Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-flu took 3.9835309982299805s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.8160552978515625e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2643911838531494s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.604194641113281e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fma took 4.037635087966919s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2735741138458252s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001366138458251953s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fypo took 4.037595748901367s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.2697618007659912s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.298324584960938e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-geospecies took 4.062330484390259s
Availability | SPARQL endpoint availability check for General Formal Ontology took 5.459785461425781e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.26728248596191406s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020796775817871094s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00017023086547851562s
Believability | Calculation of trust value for General Formal Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gfo took 3.892310619354248s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.38690185546875e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.25815820693969727s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.02093219757080078s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006089210510253906s
Believability | Calculation of trust value for General Formal Ontology: Biology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 3.7741081714630127s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.506111145019531e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.26349377632141113s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008826255798339844s
Believability | Calculation of trust value for Gene Ontology Extension took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-go_x1 took 3.8524599075317383s
Availability | SPARQL endpoint availability check for Gene Ontology took 7.104873657226562e-05s
Availability | VoID file availability check for Gene Ontology took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.262101411819458s
Reputation | Calculation of the PageRank for Gene Ontology took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008542537689208984s
Believability | Calculation of trust value for Gene Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-go_x2 took 4.081709861755371s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.267692565917969e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.26415133476257324s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.021034717559814453s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0011317729949951172s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 4.100799560546875e-05s
Believability | Calculation of trust value for Cereal Plant Development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gro took 3.908111333847046s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 7.2479248046875e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.25488996505737305s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00044035911560058594s
Believability | Calculation of trust value for Cereal plant gross anatomy took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-gro_x1 took 4.043059825897217s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2646305561065674s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02082538604736328s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007603168487548828s
Believability | Calculation of trust value for Gene Regulation Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-gro_x2 took 3.868055582046509s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.24822092056274414s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02035689353942871s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005588531494140625s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hao took 3.85634183883667s
Availability | SPARQL endpoint availability check for HCPCS took 4.506111145019531e-05s
Availability | VoID file availability check for HCPCS took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2532329559326172s
Reputation | Calculation of the PageRank for HCPCS took 0.020503759384155273s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0008320808410644531s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00027060508728027344s
Believability | Calculation of trust value for HCPCS took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-hcpcs took 3.829704523086548s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.5299530029296875e-05s
Availability | VoID file availability check for Health Level Seven took 0.000766754150390625s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.2563972473144531s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012941360473632812s
Believability | Calculation of trust value for Health Level Seven took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-hl7 took 3.8976569175720215s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.4345855712890625e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.29303932189941406s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003619194030761719s
Believability | Calculation of trust value for HEALTH_INDICATORS took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hlth_indics took 3.873412609100342s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.5299530029296875e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2702488899230957s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.02123737335205078s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0008449554443359375s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.504753112792969e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-hom took 3.923739194869995s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.410743713378906e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.24789977073669434s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020707130432128906s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.266334533691406e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-hom_harvard took 4.063560724258423s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.2830936908721924s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006594657897949219s
Believability | Calculation of trust value for Human Phenotype Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-hp_x1 took 4.019942045211792s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.2544240951538086s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0011115074157714844s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-hpio took 3.881204605102539s
Availability | SPARQL endpoint availability check for HUGO took 4.458427429199219e-05s
Availability | VoID file availability check for HUGO took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for HUGO took 0.28363847732543945s
Reputation | Calculation of the PageRank for HUGO took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for HUGO took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0010290145874023438s
Interlinking | Calculation of Clustering coefficient for HUGO took 0.00010013580322265625s
Believability | Calculation of trust value for HUGO took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hugo took 3.7705881595611572s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.259533166885376s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.021685361862182617s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006835460662841797s
Believability | Calculation of trust value for Information Artifact Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-iao took 3.860524892807007s
Availability | SPARQL endpoint availability check for ICD10 took 4.482269287109375e-05s
Availability | VoID file availability check for ICD10 took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for ICD10 took 0.25559067726135254s
Reputation | Calculation of the PageRank for ICD10 took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008404254913330078s
Believability | Calculation of trust value for ICD10 took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icd10 took 3.9575531482696533s
Availability | SPARQL endpoint availability check for ICD10CM took 4.38690185546875e-05s
Availability | VoID file availability check for ICD10CM took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.27182602882385254s
Reputation | Calculation of the PageRank for ICD10CM took 0.021373271942138672s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006778240203857422s
Believability | Calculation of trust value for ICD10CM took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd10cm took 4.031062364578247s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.267692565917969e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.26206374168395996s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0008752346038818359s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.0001850128173828125s
Believability | Calculation of trust value for ICD-10-PCS took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icd10pcs took 3.7201409339904785s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.2639195919036865s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0007128715515136719s
Believability | Calculation of trust value for International Classification of Diseases took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icd9cm took 3.9572150707244873s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.5299530029296875e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0008122920989990234s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.25492262840270996s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.022475242614746094s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0005176067352294922s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icf_x1 took 4.216881513595581s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.25851893424987793s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.021352767944335938s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0008397102355957031s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0013151168823242188s
Believability | Calculation of trust value for International Classification for Nursing Practice took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icnp took 3.784702777862549s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 7.486343383789062e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2559776306152344s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020875930786132812s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004582405090332031s
Believability | Calculation of trust value for International Classification of Primary Care took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icpc took 3.845519781112671s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.4345855712890625e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.27788805961608887s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008966922760009766s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icpc2p took 4.005308628082275s
Availability | SPARQL endpoint availability check for ICPS Network took 4.482269287109375e-05s
Availability | VoID file availability check for ICPS Network took 0.0007460117340087891s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.25559210777282715s
Reputation | Calculation of the PageRank for ICPS Network took 0.02076578140258789s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0008385181427001953s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00023865699768066406s
Believability | Calculation of trust value for ICPS Network took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icps took 3.948005437850952s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2703824043273926s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008463859558105469s
Believability | Calculation of trust value for Infectious Disease Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ido took 3.834117889404297s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2773568630218506s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020676374435424805s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011782646179199219s
Believability | Calculation of trust value for Brucellosis Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-idobru took 4.022933483123779s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.255418062210083s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013053417205810547s
Believability | Calculation of trust value for Malaria Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-idomal took 3.965545654296875s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.410743713378906e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2478022575378418s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00030040740966796875s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-iev took 3.894026756286621s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.863739013671875e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0008075237274169922s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2685556411743164s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015497207641601562s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-imgt took 4.1579062938690186s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.5299530029296875e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2672238349914551s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005831718444824219s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-imr took 3.925579786300659s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2782306671142578s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007805824279785156s
Believability | Calculation of trust value for Interaction Network Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ino took 3.788738965988159s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.220008850097656e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.27015185356140137s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.719329833984375e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-invertebrata took 3.735938787460327s
Availability | SPARQL endpoint availability check for IxnO took 5.364418029785156e-05s
Availability | VoID file availability check for IxnO took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for IxnO took 0.2747020721435547s
Reputation | Calculation of the PageRank for IxnO took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00022029876708984375s
Believability | Calculation of trust value for IxnO took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ixno took 3.7326390743255615s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.458427429199219e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2521498203277588s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00040221214294433594s
Believability | Calculation of trust value for SysMO-JERM took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-jerm took 3.9041779041290283s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2539994716644287s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-kisao took 3.9450571537017822s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 5.650520324707031e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2755730152130127s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00020051002502441406s
Believability | Calculation of trust value for Loggerhead nesting took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-lhn took 3.7937772274017334s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.25563549995422363s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020384788513183594s
Believability | Calculation of trust value for Lipid Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-lipro took 4.069851398468018s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 5.555152893066406e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.00039315223693847656s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3034687042236328s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0019421577453613281s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-lnc took 4.793359279632568s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2557234764099121s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006461143493652344s
Believability | Calculation of trust value for Mouse adult gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ma took 4.142378807067871s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.38690185546875e-05s
Availability | VoID file availability check for Multiple alignment took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.27457547187805176s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0001976490020751953s
Believability | Calculation of trust value for Multiple alignment took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mao took 3.959994077682495s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.38690185546875e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.24895548820495605s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007216930389404297s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mat took 3.875077247619629s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.291534423828125e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.25579380989074707s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004451274871826172s
Believability | Calculation of trust value for Breast tissue cell lines took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mcbcc took 4.036602258682251s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.24301481246948242s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007414817810058594s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl took 3.951132297515869s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26374340057373047s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014560222625732422s
Believability | Calculation of trust value for Cell line ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 3.7312982082366943s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 5.435943603515625e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.2410869598388672s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020793676376342773s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002498626708984375s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mcv took 3.853856325149536s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.363059997558594e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2768542766571045s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.000179290771484375s
Believability | Calculation of trust value for Master Drug Data Base took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mddb took 4.115480184555054s
Availability | SPARQL endpoint availability check for MedDRA took 4.220008850097656e-05s
Availability | VoID file availability check for MedDRA took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2738192081451416s
Reputation | Calculation of the PageRank for MedDRA took 0.022016048431396484s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011816024780273438s
Believability | Calculation of trust value for MedDRA took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mdr took 3.9219181537628174s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.601478576660156e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2613990306854248s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02040386199951172s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009202957153320312s
Believability | Calculation of trust value for MedlinePlus Health Topics took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-medlineplus took 3.87372088432312s
Availability | SPARQL endpoint availability check for MeGO took 4.315376281738281e-05s
Availability | VoID file availability check for MeGO took 0.000835418701171875s
Completeness | Calculation of interlinking completeness for MeGO took 0.24658751487731934s
Reputation | Calculation of the PageRank for MeGO took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0009288787841796875s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00019812583923339844s
Believability | Calculation of trust value for MeGO took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mego took 3.9631052017211914s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.553794860839844e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0007946491241455078s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3210115432739258s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018723011016845703s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 4.629694223403931s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 8.058547973632812e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.25525951385498047s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006444454193115234s
Believability | Calculation of trust value for Mental Functioning Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mf took 3.9505836963653564s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.4345855712890625e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2589125633239746s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005619525909423828s
Believability | Calculation of trust value for Medaka fish anatomy and development took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-mfo took 3.858335494995117s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.25668954849243164s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.021074771881103516s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0008654594421386719s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0008363723754882812s
Believability | Calculation of trust value for Emotion Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-mfoem took 4.046992301940918s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2592947483062744s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02051401138305664s
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.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010609626770019531s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mhc took 4.115564346313477s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.38690185546875e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.26772165298461914s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006794929504394531s
Believability | Calculation of trust value for Protein-protein interaction took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-mi took 3.8446264266967773s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.363059997558594e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2765016555786133s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007309913635253906s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-miro took 3.9746170043945312s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.25885438919067383s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00014638900756835938s
Believability | Calculation of trust value for Measurement Method Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mmo took 3.7626407146453857s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for MGED Ontology took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.2685701847076416s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.00041961669921875s
Believability | Calculation of trust value for MGED Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-mo took 4.72668719291687s
Availability | SPARQL endpoint availability check for Protein modification took 5.0067901611328125e-05s
Availability | VoID file availability check for Protein modification took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2405109405517578s
Reputation | Calculation of the PageRank for Protein modification took 0.020518064498901367s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00022292137145996094s
Believability | Calculation of trust value for Protein modification took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mod took 3.951427698135376s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.458427429199219e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.2570044994354248s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02111363410949707s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006988048553466797s
Believability | Calculation of trust value for Mammalian phenotype took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mp took 3.941854238510132s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.2438507080078125e-05s
Availability | VoID file availability check for Mouse pathology took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.28054118156433105s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0005102157592773438s
Believability | Calculation of trust value for Mouse pathology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mpath took 3.9794819355010986s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.1961669921875e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2489783763885498s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003643035888671875s
Believability | Calculation of trust value for Mass spectrometry took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ms took 3.889683485031128s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.458427429199219e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.33418941497802734s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0019142627716064453s
Believability | Calculation of trust value for Medical Subject Headings took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-msh took 4.566251754760742s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 7.486343383789062e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.00040793418884277344s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2806069850921631s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001823902130126953s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mthch took 4.071548223495483s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 5.1975250244140625e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.2614126205444336s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.021429777145385742s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0008518695831298828s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0010199546813964844s
Believability | Calculation of trust value for Natural Products Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-natpro took 3.804659843444824s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.506111145019531e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2623283863067627s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008103847503662109s
Believability | Calculation of trust value for NCBI organismal classification took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 3.9491913318634033s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.363059997558594e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3099358081817627s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.002018451690673828s
Believability | Calculation of trust value for NCI Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ncit took 4.510178327560425s
Availability | SPARQL endpoint availability check for National Drug Data File took 5.507469177246094e-05s
Availability | VoID file availability check for National Drug Data File took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.2738456726074219s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02073216438293457s
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.0008254051208496094s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0007150173187255859s
Believability | Calculation of trust value for National Drug Data File took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nddf took 3.947676658630371s
Availability | SPARQL endpoint availability check for National Drug File took 4.601478576660156e-05s
Availability | VoID file availability check for National Drug File took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2594590187072754s
Reputation | Calculation of the PageRank for National Drug File took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for National Drug File took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012404918670654297s
Believability | Calculation of trust value for National Drug File took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ndfrt took 4.1005918979644775s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.410743713378906e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.24563074111938477s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020896434783935547s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011572837829589844s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 4.037691593170166s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2823195457458496s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006527900695800781s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-neomark took 4.086427688598633s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 5.793571472167969e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.27741336822509766s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012540817260742188s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-neomarkontology took 3.9639627933502197s
Availability | SPARQL endpoint availability check for NIFSTD took 4.458427429199219e-05s
Availability | VoID file availability check for NIFSTD took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.31557393074035645s
Reputation | Calculation of the PageRank for NIFSTD took 0.02131366729736328s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019659996032714844s
Believability | Calculation of trust value for NIFSTD took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif took 4.452923774719238s
Availability | SPARQL endpoint availability check for NIF Cell took 8.702278137207031e-05s
Availability | VoID file availability check for NIF Cell took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2591848373413086s
Reputation | Calculation of the PageRank for NIF Cell took 0.02055811882019043s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0014257431030273438s
Believability | Calculation of trust value for NIF Cell took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-nif_cell took 4.127383232116699s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.506111145019531e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.2647867202758789s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014176368713378906s
Believability | Calculation of trust value for NIF Dysfunction took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 3.816272258758545s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.24772357940673828s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02038407325744629s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005512237548828125s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-nigo took 3.82374906539917s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.2438507080078125e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.00037384033203125s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.25481176376342773s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005636215209960938s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 3.933906555175781e-05s
INFO | --- Analysis for bioportal-nmr took 3.9413864612579346s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2821822166442871s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011134147644042969s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 4.1343958377838135s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.2798161506652832s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012047290802001953s
Believability | Calculation of trust value for NanoParticle Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-npo took 3.7279887199401855s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.315376281738281e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2446126937866211s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007343292236328125s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-oae took 4.607839107513428s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.4345855712890625e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.2659578323364258s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.001486063003540039s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-obi took 4.047201871871948s
Availability | SPARQL endpoint availability check for OBOE took 4.5299530029296875e-05s
Availability | VoID file availability check for OBOE took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for OBOE took 0.27759265899658203s
Reputation | Calculation of the PageRank for OBOE took 0.020262956619262695s
Interlinking | Calculation of Degree of Connection for OBOE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010967254638671875s
Believability | Calculation of trust value for OBOE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oboe took 3.809459686279297s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.2438507080078125e-05s
Availability | VoID file availability check for OBOE SBC took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.27707982063293457s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007958412170410156s
Believability | Calculation of trust value for OBOE SBC took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 3.8895864486694336s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0008158683776855469s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2896895408630371s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005917549133300781s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ocre took 4.0386645793914795s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.4345855712890625e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.25815773010253906s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008521080017089844s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-odgi took 4.323982238769531s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 6.580352783203125e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.27913904190063477s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0009136199951171875s
Believability | Calculation of trust value for Ontology for Genetic Interval took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ogi took 4.290497541427612s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.27034640312194824s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00029540061950683594s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ogmd took 3.912259340286255s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.2960078716278076s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006852149963378906s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ogms took 3.741016149520874s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.5299530029296875e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.26867151260375977s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011243820190429688s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omim took 4.01277756690979s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.6253204345703125e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.27779579162597656s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020305871963500977s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003745555877685547s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-omit took 3.8860440254211426s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 5.1975250244140625e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.26249146461486816s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005977153778076172s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-omrse took 2.2879910469055176s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.601478576660156e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.27138423919677734s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0008034706115722656s
Believability | Calculation of trust value for Ontology of Data Mining took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ontodm took 3.9677209854125977s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 5.459785461425781e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0003986358642578125s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.27980685234069824s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 0.00010848045349121094s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00025534629821777344s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ontodt took 3.814033031463623s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.3392181396484375e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2687714099884033s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.02042412757873535s
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.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006277561187744141s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ontoorpha took 3.833864450454712s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2476024627685547s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009353160858154297s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-opl took 4.116612911224365s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.38690185546875e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.25833868980407715s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008585453033447266s
Believability | Calculation of trust value for Phenotypic quality took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pato took 3.8876140117645264s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.5299530029296875e-05s
Availability | VoID file availability check for Physician Data Query took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.25560855865478516s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020238876342773438s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008451938629150391s
Believability | Calculation of trust value for Physician Data Query took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pdq took 3.9652342796325684s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.38690185546875e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.28024721145629883s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008287429809570312s
Believability | Calculation of trust value for Pediatric Terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pedterm took 3.96103572845459s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.839897155761719e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2598600387573242s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020876646041870117s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019478797912597656s
Believability | Calculation of trust value for Parasite Experiment Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-peo took 3.844524383544922s
Availability | SPARQL endpoint availability check for PHARE took 5.3882598876953125e-05s
Availability | VoID file availability check for PHARE took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for PHARE took 0.25472593307495117s
Reputation | Calculation of the PageRank for PHARE took 0.02160811424255371s
Interlinking | Calculation of Degree of Connection for PHARE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0008082389831542969s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006575584411621094s
Believability | Calculation of trust value for PHARE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-phare took 3.758737087249756s
Availability | SPARQL endpoint availability check for PKO_Re took 4.38690185546875e-05s
Availability | VoID file availability check for PKO_Re took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2610325813293457s
Reputation | Calculation of the PageRank for PKO_Re took 0.020658493041992188s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00017571449279785156s
Believability | Calculation of trust value for PKO_Re took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pko took 4.015539169311523s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.291534423828125e-05s
Availability | VoID file availability check for PMA 2010 took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2698831558227539s
Reputation | Calculation of the PageRank for PMA 2010 took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009055137634277344s
Believability | Calculation of trust value for PMA 2010 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pma took 3.8170573711395264s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.553794860839844e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0004055500030517578s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.29456377029418945s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00016808509826660156s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pmr took 3.788607358932495s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0007677078247070312s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.27390336990356445s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.021024703979492188s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0009126663208007812s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0004382133483886719s
Believability | Calculation of trust value for Plant Anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-po took 4.096118211746216s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.4345855712890625e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2685661315917969s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.914138793945312e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-po_x1 took 3.913191080093384s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Plant Ontology took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.2552921772003174s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020227432250976562s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00046896934509277344s
Believability | Calculation of trust value for Plant Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-po_x2 took 3.923666000366211s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.458427429199219e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2663438320159912s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006616115570068359s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pr took 3.962123394012451s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.267692565917969e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.24859833717346191s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020674467086791992s
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.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002598762512207031s
Believability | Calculation of trust value for Proteomics data and process provenance took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-propreo took 3.819498300552368s
Availability | SPARQL endpoint availability check for Pathway ontology took 5.2928924560546875e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.2892184257507324s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020440340042114258s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00015282630920410156s
Believability | Calculation of trust value for Pathway ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pw took 3.955071449279785s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.26483941078186035s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-qibo took 3.969601631164551s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.2438507080078125e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.31492042541503906s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020748376846313477s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0008189678192138672s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.001798868179321289s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rcd took 4.229335308074951s
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.0006873607635498047s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2620999813079834s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02087092399597168s
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.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00013327598571777344s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rctontology took 4.061998605728149s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 6.270408630371094e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0007596015930175781s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.25566530227661133s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.655952453613281e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-repo took 4.002013683319092s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.291534423828125e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.25650930404663086s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0001919269561767578s
Believability | Calculation of trust value for Physico-chemical process took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rex took 3.9654006958007812s
Availability | SPARQL endpoint availability check for RadLex took 4.3392181396484375e-05s
Availability | VoID file availability check for RadLex took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for RadLex took 0.2492504119873047s
Reputation | Calculation of the PageRank for RadLex took 0.020909786224365234s
Interlinking | Calculation of Degree of Connection for RadLex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0016121864318847656s
Believability | Calculation of trust value for RadLex took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rid took 3.9176554679870605s
Availability | SPARQL endpoint availability check for RNA ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for RNA ontology took 0.0012094974517822266s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2558269500732422s
Reputation | Calculation of the PageRank for RNA ontology took 0.020669937133789062s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0010023117065429688s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0006754398345947266s
Believability | Calculation of trust value for RNA ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rnao took 3.836012363433838s
Availability | SPARQL endpoint availability check for Role Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Role Ontology took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2791616916656494s
Reputation | Calculation of the PageRank for Role Ontology took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0008838176727294922s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00021123886108398438s
Believability | Calculation of trust value for Role Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-roleo took 3.9286489486694336s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.2585616111755371s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001761913299560547s
Believability | Calculation of trust value for Rat Strain Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rs took 4.050353050231934s
Availability | SPARQL endpoint availability check for RxNORM took 5.7220458984375e-05s
Availability | VoID file availability check for RxNORM took 0.00083160400390625s
Completeness | Calculation of interlinking completeness for RxNORM took 0.24801278114318848s
Reputation | Calculation of the PageRank for RxNORM took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006499290466308594s
Believability | Calculation of trust value for RxNORM took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rxnorm took 3.9918570518493652s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.267692565917969e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.24654507637023926s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0009415149688720703s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0011298656463623047s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sao took 4.0695765018463135s
Availability | SPARQL endpoint availability check for Systems Biology took 4.267692565917969e-05s
Availability | VoID file availability check for Systems Biology took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.2877960205078125s
Reputation | Calculation of the PageRank for Systems Biology took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for Systems Biology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004963874816894531s
Believability | Calculation of trust value for Systems Biology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sbo took 3.7712957859039307s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.26840996742248535s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0009045600891113281s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010824203491210938s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sbro took 4.014216661453247s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.2700204849243164s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.0203554630279541s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013606548309326172s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sdo took 3.8878135681152344s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.410743713378906e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2808258533477783s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.020653724670410156s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00035572052001953125s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sep took 3.9299399852752686s
Availability | SPARQL endpoint availability check for Student Health Record took 4.458427429199219e-05s
Availability | VoID file availability check for Student Health Record took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.27259278297424316s
Reputation | Calculation of the PageRank for Student Health Record took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.000461578369140625s
Believability | Calculation of trust value for Student Health Record took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-shr took 3.9129221439361572s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2675051689147949s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0009644031524658203s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0013628005981445312s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-sio took 5.109166383743286s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.2438507080078125e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2582376003265381s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02048015594482422s
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.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.000225067138671875s
Believability | Calculation of trust value for Situation-Based Access Control took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sitbac took 3.790558338165283s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.38690185546875e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.30223512649536133s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019295215606689453s
Believability | Calculation of trust value for SNOMED Clinical Terms took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-snomedct took 4.298429727554321s
Availability | SPARQL endpoint availability check for SNP-Ontology took 6.151199340820312e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.26821470260620117s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.000675201416015625s
Believability | Calculation of trust value for SNP-Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-snpo took 4.158759355545044s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.458427429199219e-05s
Availability | VoID file availability check for Sequence types and features took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.25774121284484863s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005846023559570312s
Believability | Calculation of trust value for Sequence types and features took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-so_x1 took 3.9542739391326904s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 5.173683166503906e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.32207584381103516s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.001622915267944336s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-sopharm took 4.3509485721588135s
Availability | SPARQL endpoint availability check for SoyOntology took 5.125999450683594e-05s
Availability | VoID file availability check for SoyOntology took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.2564425468444824s
Reputation | Calculation of the PageRank for SoyOntology took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00013208389282226562s
Believability | Calculation of trust value for SoyOntology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-soy took 4.006069898605347s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Spider Ontology took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.28082895278930664s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003273487091064453s
Believability | Calculation of trust value for Spider Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-spd took 3.822888135910034s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2583339214324951s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00027680397033691406s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-spto took 3.923290967941284s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.27000880241394043s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00044465065002441406s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sso took 3.930185317993164s
Availability | SPARQL endpoint availability check for Software Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Software Ontology took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2559473514556885s
Reputation | Calculation of the PageRank for Software Ontology took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00042700767517089844s
Believability | Calculation of trust value for Software Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-swo took 4.112013101577759s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.28208446502685547s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002455711364746094s
Believability | Calculation of trust value for Tick gross anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-tads took 4.06010103225708s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.27146196365356445s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0009050369262695312s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tao took 3.979203462600708s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.744529724121094e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0007660388946533203s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.25360822677612305s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.012222290039062e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-taxrank took 4.033517360687256s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.38690185546875e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.369128942489624s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0009932518005371094s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 0.00013065338134765625s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-teddy took 3.9104456901550293s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0008454322814941406s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2663085460662842s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008466243743896484s
Believability | Calculation of trust value for Time Event Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-teo took 3.8028945922851562s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.601478576660156e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.25916194915771484s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020395517349243164s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003941059112548828s
Believability | Calculation of trust value for Mosquito gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tgma took 3.986919403076172s
Availability | SPARQL endpoint availability check for thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for thesaurus took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for thesaurus took 0.24779796600341797s
Reputation | Calculation of the PageRank for thesaurus took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.747245788574219e-05s
Believability | Calculation of trust value for thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-thesaurus took 3.836339235305786s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 5.745887756347656e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.2733042240142822s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003418922424316406s
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 3.9552316665649414s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2594466209411621s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008320808410644531s
Believability | Calculation of trust value for Translational Medicine Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tmo took 3.986433267593384s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.24139070510864258s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015616416931152344s
Believability | Calculation of trust value for Plant Trait Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-to took 3.7548279762268066s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2577495574951172s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00019049644470214844s
Believability | Calculation of trust value for TOK_Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tok took 3.7813560962677s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.482269287109375e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0009095668792724609s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.26352882385253906s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00022268295288085938s
Believability | Calculation of trust value for Teleost taxonomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-tto took 4.064401626586914s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2545347213745117s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010476112365722656s
Believability | Calculation of trust value for Uber anatomy ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-uberon took 3.947983980178833s
Availability | SPARQL endpoint availability check for Units Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Units Ontology took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.29761600494384766s
Reputation | Calculation of the PageRank for Units Ontology took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002231597900390625s
Believability | Calculation of trust value for Units Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-unitsontology took 4.341804504394531s
Availability | SPARQL endpoint availability check for Units of measurement took 4.315376281738281e-05s
Availability | VoID file availability check for Units of measurement took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.25306034088134766s
Reputation | Calculation of the PageRank for Units of measurement took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0003085136413574219s
Believability | Calculation of trust value for Units of measurement took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-uo took 3.9842095375061035s
Availability | SPARQL endpoint availability check for VANDF took 4.291534423828125e-05s
Availability | VoID file availability check for VANDF took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for VANDF took 0.26715850830078125s
Reputation | Calculation of the PageRank for VANDF took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for VANDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VANDF took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006988048553466797s
Believability | Calculation of trust value for VANDF took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vandf took 4.396091461181641s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 7.796287536621094e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.24929118156433105s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00047206878662109375s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vao took 4.075004577636719s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 7.796287536621094e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0007791519165039062s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.268904447555542s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0008389949798583984s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006272792816162109s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vhog took 3.9739391803741455s
Availability | SPARQL endpoint availability check for VIVO took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for VIVO took 0.23472380638122559s
Reputation | Calculation of the PageRank for VIVO took 0.020800113677978516s
Interlinking | Calculation of Degree of Connection for VIVO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0008800029754638672s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003619194030761719s
Believability | Calculation of trust value for VIVO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vivo took 4.018289566040039s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.26874852180480957s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02063608169555664s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0008401870727539062s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.001348733901977539s
Believability | Calculation of trust value for Vaccine Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vo took 4.150822401046753s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2646481990814209s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.021586894989013672s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00021696090698242188s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-vt took 3.995236873626709s
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.0006046295166015625s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2520313262939453s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005016326904296875s
Believability | Calculation of trust value for C. elegans gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-wbbt took 3.8553988933563232s
Availability | SPARQL endpoint availability check for C. elegans development took 4.3392181396484375e-05s
Availability | VoID file availability check for C. elegans development took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2596867084503174s
Reputation | Calculation of the PageRank for C. elegans development took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.4345855712890625e-05s
Believability | Calculation of trust value for C. elegans development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-wbls took 4.019726991653442s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.315376281738281e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2757713794708252s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.012222290039062e-05s
Believability | Calculation of trust value for C. elegans phenotype took 7.62939453125e-06s
INFO | --- Analysis for bioportal-wbphenotype took 4.969579219818115s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.38690185546875e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0007374286651611328s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2564220428466797s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.00058746337890625s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-who took 3.9859213829040527s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 8.821487426757812e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0007748603820800781s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.27728939056396484s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020842552185058594s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006983280181884766s
Believability | Calculation of trust value for Xenopus anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-xao took 3.9159133434295654s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.25209784507751465s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020434141159057617s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00024080276489257812s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-xco took 3.904085874557495s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 8.7738037109375e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.25678038597106934s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00026035308837890625s
Believability | Calculation of trust value for Yeast phenotypes took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ypo took 3.752824068069458s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.38690185546875e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2727499008178711s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007853507995605469s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-zfa took 3.9283394813537598s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4478428363800049s
Availability | VoID file availability check for BioSamples RDF took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2377016544342041s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02114105224609375s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for BioSamples RDF took 8.58306884765625e-06s
INFO | --- Analysis for biosamples-rdf took 3.3507730960845947s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.9004848003387451s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.25426459312438965s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011873245239257812s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.5497207641601562e-05s
INFO | --- Analysis for bis-linked-data took 3.24088191986084s
Availability | SPARQL endpoint availability check for Bitzi took 4.3392181396484375e-05s
Availability | VoID file availability check for Bitzi took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Bitzi took 0.2825005054473877s
Reputation | Calculation of the PageRank for Bitzi took 0.021023035049438477s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.147125244140625e-05s
Believability | Calculation of trust value for Bitzi took 6.9141387939453125e-06s
INFO | --- Analysis for bitzi took 2.9072835445404053s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.291534423828125e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.26716113090515137s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.337860107421875e-05s
Believability | Calculation of trust value for BizkaiSense took 8.344650268554688e-06s
INFO | --- Analysis for bizkaisense took 2.9021682739257812s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.2438507080078125e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2938106060028076s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.24249267578125e-05s
Believability | Calculation of trust value for blabla.itemlist took 6.9141387939453125e-06s
INFO | --- Analysis for blabla-itemlist took 2.9280807971954346s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.172325134277344e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.26563429832458496s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02074432373046875s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.218650817871094e-05s
Believability | Calculation of trust value for blabla.itemlist took 6.67572021484375e-06s
INFO | --- Analysis for blabla_itemlist took 2.8404314517974854s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.2943274974822998s
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.2793700695037842s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.4849853515625e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for bluk-bnb took 11.395882844924927s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6552426815032959s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0003962516784667969s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.812549114227295s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3110718727111816s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.578219175338745s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.035457372665405s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.41159534454346s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.2323977947235107s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5475358963012695s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.49297451972961426s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5802822113037109s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5754096508026123s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7728397846221924s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.43410921096802s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4508328437805176s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0443670749664307s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.128425121307373s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8716833591461182s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.587515115737915s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6272568702697754s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.63015365600586s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.961822509765625e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.47319602966308594s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5186841487884521s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.44347143173217773s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6393857002258301s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.570641040802002s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2607226371765137s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7659766674041748s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.44382905960083s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8195624351501465s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8889353275299072s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4497184753417969s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9143683910369873s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03088545799255371s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.027915477752685547s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.45404505729675293s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.359797954559326s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.226468801498413s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.2121264934539795s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3176312446594238s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.564260005950928s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030411720275878906s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5023024082183838s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.153315305709839s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.720834493637085s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3602313995361328s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.34600830078125e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.867813110351562e-06s
INFO | --- Analysis for bpr took 489.62304306030273s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.38690185546875e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.26731252670288086s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.842613220214844e-05s
Believability | Calculation of trust value for Brazilian Politicians took 5.245208740234375e-06s
INFO | --- Analysis for brazilian-politicians took 3.1002185344696045s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.410743713378906e-05s
Availability | VoID file availability check for BrazilianCities took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.25826096534729004s
Reputation | Calculation of the PageRank for BrazilianCities took 0.02030467987060547s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.0040740966796875e-05s
Believability | Calculation of trust value for BrazilianCities took 7.867813110351562e-06s
INFO | --- Analysis for braziliancities took 2.7961575984954834s
Availability | SPARQL endpoint availability check for Bricklink took 1.580873966217041s
Availability | VoID file availability check for Bricklink took 0.00041222572326660156s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2548563480377197s
Reputation | Calculation of the PageRank for Bricklink took 0.022545337677001953s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0008959770202636719s
Interlinking | Calculation of Clustering coefficient for Bricklink took 8.821487426757812e-05s
Believability | Calculation of trust value for Bricklink took 1.0251998901367188e-05s
INFO | --- Analysis for bricklink took 10.887364625930786s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.182218074798584s
Availability | VoID file availability check for British Museum Collection took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2595787048339844s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.147125244140625e-05s
Believability | Calculation of trust value for British Museum Collection took 1.1920928955078125e-05s
INFO | --- Analysis for british-museum-collection took 73.00168800354004s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.482269287109375e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.25064516067504883s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.910064697265625e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 9.298324584960938e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.8335700035095215s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.38690185546875e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.2706465721130371s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0008778572082519531s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 3.170967102050781e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 8.344650268554688e-06s
INFO | --- Analysis for bsv took 2.966827154159546s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.4345855712890625e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.25740981101989746s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 7.62939453125e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.847130298614502s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.673004150390625e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.26996493339538574s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 2.956390380859375e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 6.4373016357421875e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 3.3498623371124268s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.4331486225128174s
Availability | VoID file availability check for business.data.gov.uk took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2968010902404785s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.125999450683594e-05s
Believability | Calculation of trust value for business.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for business-data-gov-uk took 2.966238260269165s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.1961669921875e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.27033567428588867s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020456314086914062s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 2.8371810913085938e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.3909759521484375e-06s
INFO | --- Analysis for cabbage took 2.93057918548584s
Availability | SPARQL endpoint availability check for cablegate took 1.643846035003662s
Availability | VoID file availability check for cablegate took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for cablegate took 0.2568814754486084s
Reputation | Calculation of the PageRank for cablegate took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for cablegate took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.033348083496094e-05s
Believability | Calculation of trust value for cablegate took 7.152557373046875e-06s
INFO | --- Analysis for cablegate took 16.3183012008667s
Availability | SPARQL endpoint availability check for Calames took 5.412101745605469e-05s
Availability | VoID file availability check for Calames took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Calames took 0.2587313652038574s
Reputation | Calculation of the PageRank for Calames took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for Calames took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Calames took 3.4332275390625e-05s
Believability | Calculation of trust value for Calames took 6.198883056640625e-06s
INFO | --- Analysis for calames took 4.016885995864868s
Availability | SPARQL endpoint availability check for can-link took 4.172325134277344e-05s
Availability | VoID file availability check for can-link took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for can-link took 0.2636539936065674s
Reputation | Calculation of the PageRank for can-link took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for can-link took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for can-link took 0.0010712146759033203s
Interlinking | Calculation of Clustering coefficient for can-link took 3.7670135498046875e-05s
Believability | Calculation of trust value for can-link took 7.62939453125e-06s
INFO | --- Analysis for can-link took 2.871575117111206s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07767486572265625s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.26412129402160645s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 7.152557373046875e-06s
INFO | --- Analysis for cap-italy-rdf took 2.535811185836792s
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.0006937980651855469s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2595798969268799s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.910064697265625e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 7.3909759521484375e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.897336006164551s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.267692565917969e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0003387928009033203s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.25133633613586426s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.1948089599609375e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 7.3909759521484375e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.908914089202881s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 7.390975952148438e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.24039793014526367s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010085105895996094s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 7.867813110351562e-06s
INFO | --- Analysis for ce4r took 16.847207069396973s
Availability | SPARQL endpoint availability check for Charging Stations took 4.220008850097656e-05s
Availability | VoID file availability check for Charging Stations took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.2524080276489258s
Reputation | Calculation of the PageRank for Charging Stations took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 2.9802322387695312e-05s
Believability | Calculation of trust value for Charging Stations took 6.9141387939453125e-06s
INFO | --- Analysis for charging-stations took 2.8690640926361084s
Availability | SPARQL endpoint availability check for Chat Game corpus took 5.412101745605469e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0012824535369873047s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.25141191482543945s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.022378206253051758s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0012042522430419922s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 4.076957702636719e-05s
Believability | Calculation of trust value for Chat Game corpus took 7.867813110351562e-06s
INFO | --- Analysis for chat-game-corpus took 12.47249460220337s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.2438507080078125e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.2380962371826172s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.409385681152344e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 8.106231689453125e-06s
INFO | --- Analysis for chebi took 2.8062586784362793s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.410743713378906e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008108615875244141s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.27644872665405273s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.602836608886719e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 7.3909759521484375e-06s
INFO | --- Analysis for chem2bio2rdf took 133.93216037750244s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.6130726337432861s
Availability | VoID file availability check for ChEMBL RDF took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.26320934295654297s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020201683044433594s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.0067901611328125e-05s
Believability | Calculation of trust value for ChEMBL RDF took 7.152557373046875e-06s
INFO | --- Analysis for chembl-rdf took 3.5858068466186523s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.4345855712890625e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.23333311080932617s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020658493041992188s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.0994415283203125e-05s
Believability | Calculation of trust value for ChemPedia RDF took 6.9141387939453125e-06s
INFO | --- Analysis for chempedia-rdf took 8.695725917816162s
Availability | SPARQL endpoint availability check for Chronicling America took 4.38690185546875e-05s
Availability | VoID file availability check for Chronicling America took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.27209925651550293s
Reputation | Calculation of the PageRank for Chronicling America took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0008392333984375s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010371208190917969s
Believability | Calculation of trust value for Chronicling America took 7.3909759521484375e-06s
INFO | --- Analysis for chronicling-america took 6.226619720458984s
Availability | SPARQL endpoint availability check for ciard-ring took 4.696846008300781e-05s
Availability | VoID file availability check for ciard-ring took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2642822265625s
Reputation | Calculation of the PageRank for ciard-ring took 0.021759748458862305s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.8160552978515625e-05s
Believability | Calculation of trust value for ciard-ring took 7.867813110351562e-06s
INFO | --- Analysis for ciard-ring took 3.2335643768310547s
Availability | SPARQL endpoint availability check for CIPFA took 4.6253204345703125e-05s
Availability | VoID file availability check for CIPFA took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for CIPFA took 0.26802706718444824s
Reputation | Calculation of the PageRank for CIPFA took 0.02093052864074707s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.647804260253906e-05s
Believability | Calculation of trust value for CIPFA took 5.245208740234375e-06s
INFO | --- Analysis for cipfa took 2.623124122619629s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 0.2554049491882324s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.24358344078063965s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00040459632873535156s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 8.344650268554688e-06s
INFO | --- Analysis for ckan took 2.8388309478759766s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.7833423614501953s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2628200054168701s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.368492126464844e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 5.9604644775390625e-06s
INFO | --- Analysis for clean-energy-data-reegle took 11.424275636672974s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.410743713378906e-05s
Availability | VoID file availability check for CLLD-afbo took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.23509860038757324s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 8.344650268554688e-05s
Believability | Calculation of trust value for CLLD-afbo took 6.198883056640625e-06s
INFO | --- Analysis for clld-afbo took 3.3032684326171875s
Availability | SPARQL endpoint availability check for CLLD-APICS took 6.008148193359375e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.26389241218566895s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.82012939453125e-05s
Believability | Calculation of trust value for CLLD-APICS took 7.3909759521484375e-06s
INFO | --- Analysis for clld-apics took 3.4282755851745605s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.482269287109375e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.26457881927490234s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.695487976074219e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 8.344650268554688e-06s
INFO | --- Analysis for clld-ewave took 4.223433017730713s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.935264587402344e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0003337860107421875s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2608640193939209s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.751319885253906e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 8.58306884765625e-06s
INFO | --- Analysis for clld-glottolog took 3.3790946006774902s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.482269287109375e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.2920725345611572s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.463859558105469e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 6.9141387939453125e-06s
INFO | --- Analysis for clld-phoible took 3.3623459339141846s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 5.6743621826171875e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.001272439956665039s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.28539252281188965s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020878314971923828s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.677078247070312e-05s
Believability | Calculation of trust value for CLLD-SAILS took 8.821487426757812e-06s
INFO | --- Analysis for clld-sails took 3.7342569828033447s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.553794860839844e-05s
Availability | VoID file availability check for CLLD-WALS took 0.00041413307189941406s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.24986958503723145s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.869171142578125e-05s
Believability | Calculation of trust value for CLLD-WALS took 9.298324584960938e-06s
INFO | --- Analysis for clld-wals took 3.431358814239502s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.4345855712890625e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.2642965316772461s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.915496826171875e-05s
Believability | Calculation of trust value for CLLD-WOLD took 8.821487426757812e-06s
INFO | --- Analysis for clld-wold took 3.7042136192321777s
Availability | SPARQL endpoint availability check for COD inventory took 4.410743713378906e-05s
Availability | VoID file availability check for COD inventory took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for COD inventory took 0.27437329292297363s
Reputation | Calculation of the PageRank for COD inventory took 0.02080535888671875s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.123283386230469e-05s
Believability | Calculation of trust value for COD inventory took 7.152557373046875e-06s
INFO | --- Analysis for cod-inventory took 2.9016013145446777s
Availability | SPARQL endpoint availability check for CODE Endpoint took 5.8650970458984375e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.2573368549346924s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.0040740966796875e-05s
Believability | Calculation of trust value for CODE Endpoint took 7.3909759521484375e-06s
INFO | --- Analysis for code-endpoint took 2.8589274883270264s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.3800792694091797s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.27153682708740234s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 2.8848648071289062e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 5.4836273193359375e-06s
INFO | --- Analysis for coins-openuplabs took 3.725896120071411s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.05694174766540527s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.2536306381225586s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.8623809814453125e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for colinda took 2.4815120697021484s
Availability | SPARQL endpoint availability check for CN  2012 took 25.666168451309204s
Availability | VoID file availability check for CN  2012 took 0.0008685588836669922s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.2709624767303467s
Reputation | Calculation of the PageRank for CN  2012 took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.100799560546875e-05s
Believability | Calculation of trust value for CN  2012 took 5.7220458984375e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 124.704749584198s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.2438507080078125e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.27979493141174316s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.029242515563964844s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.001119852066040039s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 4.220008850097656e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 7.3909759521484375e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 2.931990385055542s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.267692565917969e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2588465213775635s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.1948089599609375e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 1.2874603271484375e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.8888533115386963s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 5.245208740234375e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.24798274040222168s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.020685434341430664s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.719329833984375e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 7.3909759521484375e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.895449161529541s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.220008850097656e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.2540726661682129s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020757675170898438s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 3.147125244140625e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 8.821487426757812e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.8752541542053223s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.315376281738281e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.2526848316192627s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.314018249511719e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 7.867813110351562e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.889735221862793s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.412705421447754s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.25824546813964844s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020768165588378906s
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.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.695487976074219e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 6.198883056640625e-06s
INFO | --- Analysis for comsode-d3-2 took 8.148802042007446s
Availability | SPARQL endpoint availability check for ConceptNet took 5.125999450683594e-05s
Availability | VoID file availability check for ConceptNet took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.23868536949157715s
Reputation | Calculation of the PageRank for ConceptNet took 0.020734786987304688s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.147125244140625e-05s
Believability | Calculation of trust value for ConceptNet took 8.106231689453125e-06s
INFO | --- Analysis for conceptnet took 2.7966737747192383s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2689826488494873s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.719329833984375e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 8.58306884765625e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.8764867782592773s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.315376281738281e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.2500154972076416s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.337860107421875e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 8.344650268554688e-06s
INFO | --- Analysis for copac-library-catalogue took 2.867486000061035s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 5.91278076171875e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.3292679786682129s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.914138793945312e-05s
Believability | Calculation of trust value for CopyrightTermBank took 8.344650268554688e-06s
INFO | --- Analysis for copyrighttermbank took 34.0948429107666s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.214843273162842s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0003573894500732422s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.26169323921203613s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.743171691894531e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 9.059906005859375e-06s
INFO | --- Analysis for core took 6.852585554122925s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.363059997558594e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.24059629440307617s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.02108287811279297s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.170967102050781e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 7.62939453125e-06s
INFO | --- Analysis for corn took 2.876929759979248s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.458427429199219e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2731623649597168s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.02089667320251465s
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.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.0517578125e-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 2.794799327850342s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 7.414817810058594e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.2582416534423828s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.123283386230469e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 6.4373016357421875e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.7664413452148438s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.4345855712890625e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.33654069900512695s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.7697296142578125e-05s
Believability | Calculation of trust value for Cornetto1.2 took 6.9141387939453125e-06s
INFO | --- Analysis for cornetto took 12.419346332550049s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.1484832763671875e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.2564656734466553s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.8371810913085938e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for corscheck took 2.8807272911071777s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.06867313385009766s
Availability | VoID file availability check for Courts thesaurus took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2680072784423828s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.914138793945312e-05s
Believability | Calculation of trust value for Courts thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for courts-thesaurus took 2.445453643798828s
Availability | SPARQL endpoint availability check for CPA 2008 took 24.856207609176636s
Availability | VoID file availability check for CPA 2008 took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.25754761695861816s
Reputation | Calculation of the PageRank for CPA 2008 took 0.020808935165405273s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.62396240234375e-05s
Believability | Calculation of trust value for CPA 2008 took 5.245208740234375e-06s
INFO | --- Analysis for cpa-2008 took 123.70407462120056s
Availability | SPARQL endpoint availability check for CPC 2008 took 24.94638180732727s
Availability | VoID file availability check for CPC 2008 took 0.0009050369262695312s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.242415189743042s
Reputation | Calculation of the PageRank for CPC 2008 took 0.02084183692932129s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.814697265625e-05s
Believability | Calculation of trust value for CPC 2008 took 5.7220458984375e-06s
INFO | --- Analysis for cpc-2008 took 123.82330751419067s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.906123638153076s
Availability | VoID file availability check for CPV  2003 took 0.0008952617645263672s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.29772353172302246s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02087259292602539s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.267692565917969e-05s
Believability | Calculation of trust value for CPV  2003 took 5.245208740234375e-06s
INFO | --- Analysis for cpv-2003 took 115.15878868103027s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.873636484146118s
Availability | VoID file availability check for CPV 2008 took 0.0009109973907470703s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.2555675506591797s
Reputation | Calculation of the PageRank for CPV 2008 took 0.02080559730529785s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.412101745605469e-05s
Believability | Calculation of trust value for CPV 2008 took 5.4836273193359375e-06s
INFO | --- Analysis for cpv-2008 took 124.16361379623413s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.4975597858429s
Availability | VoID file availability check for crowdsourcing-fb took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.7065455913543701s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.220008850097656e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.239776611328125e-05s
INFO | --- Analysis for crowdsourcing-fb took 535.865293264389s
Availability | SPARQL endpoint availability check for CRTM took 5.1021575927734375e-05s
Availability | VoID file availability check for CRTM took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for CRTM took 0.7200667858123779s
Reputation | Calculation of the PageRank for CRTM took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for CRTM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CRTM took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.9325485229492188e-05s
Believability | Calculation of trust value for CRTM took 8.106231689453125e-06s
INFO | --- Analysis for crtm took 4.695579290390015s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.25255322456359863s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 8.344650268554688e-06s
INFO | --- Analysis for crystal-eye took 3.7518231868743896s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.7227137088775635s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.31656312942504883s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.76837158203125e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 5.7220458984375e-06s
INFO | --- Analysis for ctic-public-dataset took 44.43017840385437s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 7.319450378417969e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.2516803741455078s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020969152450561523s
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.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.4809112548828125e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.152557373046875e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 2.898754358291626s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 2.461756467819214s
Availability | VoID file availability check for CulturaLinkedData took 0.0005583763122558594s
Extra | Recovery of all triples for CulturaLinkedData took 154.46119666099548s
Performance | Total latancy measurement for CulturaLinkedData took 0.908001184463501s
Amount of data | Number of triples check for CulturaLinkedData took 3.1277658939361572s
Interoperability | New terms check for CulturaLinkedData took 4.118849039077759s
Versatility | Languages check for CulturaLinkedData took 62.55585861206055s
Interpretability | Number of blank nodes check for CulturaLinkedData took 1.915703296661377s
Interpretability | RDF structures check for CulturaLinkedData took 0.5890750885009766s
Versatility | Serialization formats check for CulturaLinkedData took 0.6295418739318848s
Availability | RDF dump link check for CulturaLinkedData took 2.0644659996032715s
License | MR license check for CulturaLinkedData took 0.8348987102508545s
License | HR license check for CulturaLinkedData took 62.191081285476685s
Amount of data | Number of property check for CulturaLinkedData took 0.20241737365722656s
Understandability | Number of label check for CulturaLinkedData took 0.9754838943481445s
Understandability | URI regex check for CulturaLinkedData took 2.3786380290985107s
Understandability | Vocabs check for CulturaLinkedData took 2.096111536026001s
Verifiability | Authors check for CulturaLinkedData took 0.3008432388305664s
Verifiability | Publishers check for CulturaLinkedData took 2.0132057666778564s
Performance | Throughput check for CulturaLinkedData took 22.968249082565308s
Amount of data | Check the number of entities for CulturaLinkedData took 3.24249267578125e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.25365519523620605s
Interlinking | sameAs chians check for CulturaLinkedData took 0.3858296871185303s
Interlinking | skos check for CulturaLinkedData took 0.5165128707885742s
Interlinking | skos check for CulturaLinkedData took 2.0479929447174072s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.3287177085876465s
Currency | Creation date check for CulturaLinkedData took 2.275362491607666s
Currency | Modification date check for CulturaLinkedData took 2.1088335514068604s
Rep.Conc. | URIs length for CulturaLinkedData took 66.71692657470703s
Interoperability | New vocabularies check for CulturaLinkedData took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.18085336685180664s
Accuracy | Check Functional Property for CulturaLinkedData took 2.069397449493408s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.1849498748779297s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 44.10872030258179s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6514885425567627s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.3408238887786865s
Consistency | Disjoint class check for CulturaLinkedData took 2.0131959915161133s
Consistency | Check Misplaced properties for CulturaLinkedData took 8.436294794082642s
Consistency | Misplaced classes for CulturaLinkedData took 4.221125364303589s
Consistency | Check Ontology hijacking for CulturaLinkedData took 42.251219749450684s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.391068935394287s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 9.495407581329346s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3922576904296875s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.1995391845703125s
Security | Sign check for CulturaLinkedData took 2.767009973526001s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 11.439935684204102s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.4829111099243164s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.020987272262573242s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.00543212890625e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.6689300537109375e-06s
Believability | Calculation of trust value for CulturaLinkedData took 8.106231689453125e-06s
INFO | --- Analysis for culturalinkeddata took 669.8097565174103s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.12447381019592285s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2389233112335205s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ares-or took 4.412789583206177s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.10467147827148438s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.267547607421875s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020519256591796875s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.552436828613281e-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 3.6120243072509766s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11689043045043945s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.6977353096008301s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.266334533691406e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 5.0067901611328125e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 4.205043077468872s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10696721076965332s
Availability | VoID file availability check for Integrated pollution registry took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.28011107444763184s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.647804260253906e-05s
Believability | Calculation of trust value for Integrated pollution registry took 4.76837158203125e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.7626259326934814s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10410475730895996s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.27974534034729004s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.3855438232421875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 5.0067901611328125e-06s
INFO | --- Analysis for cz-contracts took 2.8059232234954834s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.100799560546875e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.25516581535339355s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.956390380859375e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-courts took 2.923923969268799s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.10950636863708496s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2358410358428955s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.3855438232421875e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-bans took 5.426325559616089s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.15258002281188965s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.25970959663391113s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.552436828613281e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.721998453140259s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.10927510261535645s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.2841033935546875s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.266334533691406e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ctia-focus took 2.786407947540283s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.11255240440368652s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.26773715019226074s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.0531158447265625e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.722595453262329s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.10913729667663574s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.24150800704956055s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.001062631607055664s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 4.1961669921875e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.849591016769409s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.160292387008667s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.25298547744750977s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.00083160400390625s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.5762786865234375e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 5.0067901611328125e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.810805320739746s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.10173511505126953s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.251784086227417s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.337860107421875e-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 2.87581205368042s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.7449991703033447s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.25000858306884766s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.5920488834381104s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.4389042854309082s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.2564675807952881s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.02120041847229004s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0009512901306152344s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.38690185546875e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.3246333599090576s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.4201931953430176s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.26566505432128906s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.719329833984375e-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.3599584102630615s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.4234142303466797s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0011279582977294922s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.28186988830566406s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02283334732055664s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0011796951293945312s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 5.316734313964844e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.4187099933624268s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3952000141143799s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.297288179397583s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.0206143856048584s
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.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.2802000045776367s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3639345169067383s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2932124137878418s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007431507110595703s
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 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-regions took 2.976243257522583s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3620316982269287s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2535688877105713s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.910064697265625e-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.2842884063720703s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.4326939582824707s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.25841569900512695s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007944107055664062s
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.245208740234375e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.2674813270568848s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.36927056312561035s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2818155288696289s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.2761435508728027s
Availability | SPARQL endpoint availability check for ATC groups took 0.11254310607910156s
Availability | VoID file availability check for ATC groups took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2934422492980957s
Reputation | Calculation of the PageRank for ATC groups took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.985664367675781e-05s
Believability | Calculation of trust value for ATC groups took 8.106231689453125e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.779348850250244s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10900235176086426s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.28145432472229004s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020825624465942383s
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.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.743171691894531e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.4836273193359375e-06s
INFO | --- Analysis for cz-fulfillments took 2.792884349822998s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.03394341468811035s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.2593531608581543s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020620346069335938s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.982948303222656e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ic took 3.3540985584259033s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.24137306213378906s
Availability | VoID file availability check for List of Czech data boxes took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.2636101245880127s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020844697952270508s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.1948089599609375e-05s
Believability | Calculation of trust value for List of Czech data boxes took 5.4836273193359375e-06s
INFO | --- Analysis for cz-list-of-databoxes took 4.256160259246826s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.22898459434509277s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2567007541656494s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.4836273193359375e-06s
INFO | --- Analysis for cz-nace took 4.2030980587005615s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.28343963623046875s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0006349086761474609s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 46.18639922142029s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8296844959259033s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.21711993217468262s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.598663330078125s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 14.61505389213562s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.47614359855651855s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.23746824264526367s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.1525180339813232s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4373037815093994s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18255925178527832s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.6048591136932373s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.21958303451538086s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2730228900909424s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4084126949310303s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2200627326965332s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2757694721221924s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3151679039001465s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 11.15546989440918s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.842613220214844e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.25705575942993164s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24466633796691895s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24649834632873535s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.34063029289245605s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.064598798751831s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5316431522369385s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.678814172744751s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 25.229319095611572s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1814286708831787s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.21889519691467285s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.209153413772583s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 21.14038896560669s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.426926612854004s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.643789529800415s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5781924724578857s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0133252143859863s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.915165901184082s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 19.292047023773193s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7262797355651855s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.0216174125671387s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.1341326236724854s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.27113842964172363s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24214482307434082s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1358.0715193748474s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.104766607284546s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8109428882598877s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.430511474609375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.4373016357421875e-06s
INFO | --- Analysis for cz-nkod took 65050.72869706154s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.203171968460083s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.268282413482666s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.0202944278717041s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.4809112548828125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 6.198883056640625e-06s
INFO | --- Analysis for cz-orders took 3.322352647781372s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.22836041450500488s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005509853363037109s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 168.22036933898926s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5931310653686523s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 87.32778835296631s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 13.441408395767212s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1028597354889s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 4.434794187545776s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.5042257308959961s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.5198948383331299s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 102.44068574905396s
License | MR license check for Institutions of public power of the Czech Republic took 0.6418709754943848s
License | HR license check for Institutions of public power of the Czech Republic took 300.15990376472473s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.16639471054077148s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 11.683496236801147s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.8307201862335205s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.380800724029541s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.504798412322998s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.28477931022644043s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.824119091033936s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.087942123413086s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.5426478385925293s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.6563191413879395s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.312786340713501s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.11890077590942383s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.24642729759216309s
Currency | Creation date check for Institutions of public power of the Czech Republic took 1.808168649673462s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.48072338104248047s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 159.46528315544128s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 11.644922256469727s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.34915614128112793s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.16466951370239258s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.15231657028198242s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 58.82081317901611s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.1364362239837646s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.6292214393615723s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.2963845729827881s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 81.08876085281372s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.723717451095581s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 36.65741491317749s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.4767553806304932s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 72.24703979492188s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6616463661193848s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.493283748626709s
Security | Sign check for Institutions of public power of the Czech Republic took 0.15143632888793945s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 524.9402103424072s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.9778504371643066s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.02310323715209961s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 9.677821636199951s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ovm took 2419.599853038788s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.11478447914123535s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0007760524749755859s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2861137390136719s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.02105879783630371s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 4.553794860839844e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 6.67572021484375e-06s
INFO | --- Analysis for cz-ovm-agendas took 4.13792872428894s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.3066270351409912s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.000308990478515625s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2657644748687744s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.961822509765625e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ruian took 5.784768104553223s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.4430112838745117s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.24671673774719238s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.021077632904052734s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.867813110351562e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 3.433690071105957s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.4803626537322998s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.26889610290527344s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.4100375175476074s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.455646276473999s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.26027345657348633s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020792245864868164s
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.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.0994415283203125e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 5.7220458984375e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.5200693607330322s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.1204228401184082s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.7407598495483398s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.021223783493041992s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.814697265625e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 3.337860107421875e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.1991007328033447s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10533595085144043s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.27289843559265137s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.021070241928100586s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.528594970703125e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.730220317840576s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11844229698181152s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2581787109375s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.02241039276123047s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.814697265625e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.8414788246154785s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.11837530136108398s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.00036406517028808594s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 177.85165166854858s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5774779319763184s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 10.879815340042114s
Interoperability | New terms check for Summary types of Czech institutions of public power took 12.57936429977417s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1190376281738s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 2.603804349899292s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.12973284721374512s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.8435378074645996s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 50.68836331367493s
License | MR license check for Summary types of Czech institutions of public power took 0.10722756385803223s
License | HR license check for Summary types of Czech institutions of public power took 298.5210509300232s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.15466523170471191s
Understandability | Number of label check for Summary types of Czech institutions of public power took 10.718897581100464s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.250302791595459s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.11826610565185547s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.18961715698242188s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.1763143539428711s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.771908044815063s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.086690902709961s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.13102960586547852s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.6221766471862793s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.170989990234375s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.11342906951904297s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.15214776992797852s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.7215502262115479s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.6073324680328369s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 153.47283744812012s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 10.740020036697388s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.35557985305786133s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.20944452285766602s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.1841449737548828s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 51.084171533584595s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.1077024936676025s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6973230838775635s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.1279757022857666s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 78.06361365318298s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.7786476612091064s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 39.82568025588989s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.3952362537384033s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 73.03044581413269s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.6726784706115723s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 1.0324914455413818s
Security | Sign check for Summary types of Czech institutions of public power took 0.11953520774841309s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 2675.1211819648743s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.5918514728546143s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.023331642150878906s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 5.817413330078125e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 9.61146855354309s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.9604644775390625e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 4382.927953243256s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.09972095489501953s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.00080108642578125s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2547414302825928s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.021016597747802734s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0009000301361083984s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.7670135498046875e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 6.198883056640625e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 3.2077226638793945s
Availability | SPARQL endpoint availability check for State funding providers took 0.1190953254699707s
Availability | VoID file availability check for State funding providers took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for State funding providers took 0.25028157234191895s
Reputation | Calculation of the PageRank for State funding providers took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.814697265625e-05s
Believability | Calculation of trust value for State funding providers took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.6000874042510986s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11774992942810059s
Availability | VoID file availability check for Organizations active in R&D took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.24599933624267578s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02144002914428711s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.029273986816406e-05s
Believability | Calculation of trust value for Organizations active in R&D took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-organizations took 3.318431854248047s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.13222670555114746s
Availability | VoID file availability check for R&D Programmes took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.32416200637817383s
Reputation | Calculation of the PageRank for R&D Programmes took 0.0209200382232666s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.9577484130859375e-05s
Believability | Calculation of trust value for R&D Programmes took 6.4373016357421875e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.913144826889038s
Availability | SPARQL endpoint availability check for R&D Projects took 0.12981891632080078s
Availability | VoID file availability check for R&D Projects took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.26136302947998047s
Reputation | Calculation of the PageRank for R&D Projects took 0.02066946029663086s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.9577484130859375e-05s
Believability | Calculation of trust value for R&D Projects took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-projects took 2.992685079574585s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11487555503845215s
Availability | VoID file availability check for Institutional research plans took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.311582088470459s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.124641418457031e-05s
Believability | Calculation of trust value for Institutional research plans took 6.4373016357421875e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.9684295654296875s
Availability | SPARQL endpoint availability check for Results of R&D took 0.12888336181640625s
Availability | VoID file availability check for Results of R&D took 0.0013773441314697266s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.2686116695404053s
Reputation | Calculation of the PageRank for Results of R&D took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.1484832763671875e-05s
Believability | Calculation of trust value for Results of R&D took 1.5735626220703125e-05s
INFO | --- Analysis for cz-vavai-results took 2.813427209854126s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.11624860763549805s
Availability | VoID file availability check for Tenders in R&D took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.26007628440856934s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.696846008300781e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.7532944679260254s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.360213041305542s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006473064422607422s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 136.1916377544403s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0254104137420654s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 23.092360734939575s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.136650085449219s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 0.22076034545898438s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.25594520568847656s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.11835646629333496s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 1.5542266368865967s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.32137632369995117s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.24518561363220215s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.24555277824401855s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 52.963181018829346s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.24647307395935059s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.8405449390411377s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.554358959197998s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.2586240768432617s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.8993206024169922s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.2373361587524414s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.275009155273438s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 5.2928924560546875e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.23872971534729004s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.39223527908325195s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.0922207832336426s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.9412219524383545s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2633500099182129s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 3.32539701461792s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.3874306678771973s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 83.25873708724976s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2446117401123047s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.6071712970733643s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.27103686332702637s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 46.25968956947327s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.1481974124908447s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.6586906909942627s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.25439953804016113s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.052047729492188s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.67832636833191s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 47.06540894508362s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4943327903747559s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 13.81289529800415s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.877894401550293s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.24581289291381836s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.25336527824401855s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 9.328017950057983s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.3980398178100586s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02150559425354004s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014638900756835938s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.2159347534179688e-05s
INFO | --- Analysis for data-bnf-fr took 652.8818609714508s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.12199735641479492s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0002853870391845703s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.9484233856201172s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.30673670768737793s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 8.356022357940674s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.268751621246338s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.0873870849609375s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.6316726207733154s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.04119110107421875s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.10748004913330078s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.0994257926940918s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.09247374534606934s
License | MR license check for Open Data from the Italian National Research Council took 0.10325837135314941s
License | HR license check for Open Data from the Italian National Research Council took 12.312861680984497s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.09256696701049805s
Understandability | Number of label check for Open Data from the Italian National Research Council took 4.074901342391968s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.17275404930114746s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.0942227840423584s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.09049177169799805s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.09142589569091797s
Performance | Throughput check for Open Data from the Italian National Research Council took 10.386600971221924s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 7.05718994140625e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.08473610877990723s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.09627509117126465s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.08510184288024902s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.06096673011779785s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.09301447868347168s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.1817646026611328s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.19297027587890625s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 12.363173484802246s
Interoperability | New vocabularies check for Open Data from the Italian National Research Council took 1.518143653869629s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.09045720100402832s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.0832054615020752s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.08510470390319824s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.4528346061706543s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.033028602600097656s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.028429031372070312s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.08552265167236328s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 10.272048473358154s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.18899297714233398s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.7168700695037842s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.3784010410308838s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 13.277070045471191s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.032866477966308594s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.8303017616271973s
Security | Sign check for Open Data from the Italian National Research Council took 0.11817431449890137s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 642.9020817279816s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.38709068298339844s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.022951602935791016s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 8.916854858398438e-05s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 1.8046221733093262s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.7220458984375e-06s
INFO | --- Analysis for data-cnr-it took 753.2413539886475s
Availability | SPARQL endpoint availability check for Data.gov took 1.3139593601226807s
Availability | VoID file availability check for Data.gov took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Data.gov took 0.28050684928894043s
Reputation | Calculation of the PageRank for Data.gov took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.0517578125e-05s
Believability | Calculation of trust value for Data.gov took 6.4373016357421875e-06s
INFO | --- Analysis for data-gov took 19.028098106384277s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.08001852035522461s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.26917243003845215s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.033348083496094e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 6.67572021484375e-06s
INFO | --- Analysis for data-gov-ie took 2.953881025314331s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 6.270408630371094e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.27032947540283203s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.271766662597656e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 5.7220458984375e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.3509459495544434s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.466803789138794s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.2830777168273926s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.0212860107421875s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.890296936035156e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 6.67572021484375e-06s
INFO | --- Analysis for data-hnm-hu took 161.29074621200562s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.11971330642700195s
Availability | VoID file availability check for Climb Dataincubator took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.27091360092163086s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.390975952148438e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-climb took 2.4497718811035156s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.13222432136535645s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007727146148681641s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.37217211723327637s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.245208740234375e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 5.245208740234375e-06s
INFO | --- Analysis for data-incubator-metoffice took 6.648116827011108s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.0546422004699707s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.24005746841430664s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.654594421386719e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-moseley took 9.510958909988403s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.053797006607055664s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.28054118156433105s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.021588563919067383s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.298324584960938e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 9.5367431640625e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.3934741020202637s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.8046367168426514s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0007793903350830078s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.2694072723388672s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 9.202957153320312e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-nasa took 10.780980110168457s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.07105064392089844s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2626192569732666s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.02048182487487793s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.557868957519531e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-our-airports took 2.42280650138855s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.0397791862487793s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.26534247398376465s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.059906005859375e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.1022279262542725s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.04779767990112305s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.24001717567443848s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.630752563476562e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.353256940841675s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.6908116340637207s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006453990936279297s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 105.96401000022888s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.3220279216766357s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 17.01297616958618s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.7037715911865234s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.29432249069214s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.32264471054077s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.15510892868041992s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.516425371170044s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.33275747299194336s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.27938389778137207s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.39565372467041016s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.37308359146118s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.9777870178222656s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.318368673324585s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.6751697063446045s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.7510280609130859s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.7386476993560791s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.9168190956115723s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.668291568756104s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 6.866455078125e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.4032878875732422s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.8746957778930664s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.597653865814209s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.4382650852203369s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.46761083602905273s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.7881159782409668s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.8440585136413574s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 51.95585322380066s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 1.1920928955078125e-05s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.41701579093933105s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.34783077239990234s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.3405003547668457s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 48.50633716583252s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.0225534439086914s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.146108627319336s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.6568348407745361s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.9557070732116699s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.06183671951294s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 42.31667709350586s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.5569746494293213s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.929572582244873s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.883349657058716s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.6242706775665283s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.49417686462402344s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.10804891586303711s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.7627310752868652s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020982027053833008s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 1.9073486328125e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 8.58306884765625e-06s
INFO | --- Analysis for data-open-ac-uk took 762.4865455627441s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.9805850982666016s
Availability | VoID file availability check for Persée in RDF took 0.0008208751678466797s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.751978874206543s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010967254638671875s
Believability | Calculation of trust value for Persée in RDF took 8.58306884765625e-06s
INFO | --- Analysis for data-persee-fr took 10.398820400238037s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.220008850097656e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.25377583503723145s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.020984888076782227s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.0517578125e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 7.62939453125e-06s
INFO | --- Analysis for data-southampton-ac-uk took 3.9712729454040527s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.1505730152130127s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.00030875205993652344s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.2443547248840332s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011467933654785156s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 9.059906005859375e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.40834903717041s
Availability | SPARQL endpoint availability check for DataFAQs took 4.5299530029296875e-05s
Availability | VoID file availability check for DataFAQs took 0.00030040740966796875s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.24213814735412598s
Reputation | Calculation of the PageRank for DataFAQs took 0.021030187606811523s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.0994415283203125e-05s
Believability | Calculation of trust value for DataFAQs took 9.059906005859375e-06s
INFO | --- Analysis for datafaqs took 2.8137121200561523s
Availability | SPARQL endpoint availability check for datahub took 4.3392181396484375e-05s
Availability | VoID file availability check for datahub took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for datahub took 0.2786839008331299s
Reputation | Calculation of the PageRank for datahub took 0.020671844482421875s
Interlinking | Calculation of Degree of Connection for datahub took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for datahub took 4.863739013671875e-05s
Believability | Calculation of trust value for datahub took 8.58306884765625e-06s
INFO | --- Analysis for datahub took 6.626128196716309s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3217151165008545s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.24354267120361328s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.176399230957031e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.3909759521484375e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 4.96488094329834s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.078182697296143s
Availability | VoID file availability check for datos-artium-org took 0.0007970333099365234s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.25957298278808594s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020770549774169922s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00012254714965820312s
Believability | Calculation of trust value for datos-artium-org took 9.775161743164062e-06s
INFO | --- Analysis for datos-artium-org took 164.68948769569397s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8890254497528076s
Availability | VoID file availability check for Datos.bcn.cl took 0.0007457733154296875s
Extra | Recovery of all triples for Datos.bcn.cl took 58.04446482658386s
Performance | Total latancy measurement for Datos.bcn.cl took 5.92243766784668s
Amount of data | Number of triples check for Datos.bcn.cl took 18.450940370559692s
Interoperability | New terms check for Datos.bcn.cl took 3.768545150756836s
Versatility | Languages check for Datos.bcn.cl took 301.03957629203796s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.6359143257141113s
Security | Check HTTPS for Datos.bcn.cl took 0.7157166004180908s
Interpretability | RDF structures check for Datos.bcn.cl took 1.5297613143920898s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2859342098236084s
Availability | RDF dump link check for Datos.bcn.cl took 1.1765007972717285s
License | MR license check for Datos.bcn.cl took 1.291740894317627s
License | HR license check for Datos.bcn.cl took 24.842069149017334s
Amount of data | Number of property check for Datos.bcn.cl took 1.2485613822937012s
Understandability | Number of label check for Datos.bcn.cl took 2.3774731159210205s
Understandability | URI regex check for Datos.bcn.cl took 2.4489495754241943s
Understandability | Vocabs check for Datos.bcn.cl took 1.2193455696105957s
Verifiability | Authors check for Datos.bcn.cl took 1.229792833328247s
Verifiability | Publishers check for Datos.bcn.cl took 1.1896424293518066s
Performance | Throughput check for Datos.bcn.cl took 11.86348009109497s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.43865966796875e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2278735637664795s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2416248321533203s
Interlinking | skos check for Datos.bcn.cl took 1.2345938682556152s
Interlinking | skos check for Datos.bcn.cl took 1.1844608783721924s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2256553173065186s
Currency | Creation date check for Datos.bcn.cl took 2.4185853004455566s
Currency | Modification date check for Datos.bcn.cl took 1.2578017711639404s
Rep.Conc. | URIs length for Datos.bcn.cl took 73.71548414230347s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.1972284317016602s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.1929688453674316s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.1919617652893066s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 21.507108688354492s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.24035429954528809s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.27401185035705566s
Consistency | Disjoint class check for Datos.bcn.cl took 1.1780033111572266s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.0400495529174805s
Consistency | Misplaced classes for Datos.bcn.cl took 2.061441421508789s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 32.95407748222351s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3685433864593506s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 6.739262342453003s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.3024556636810303s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4051170349121094s
Security | Sign check for Datos.bcn.cl took 1.2310192584991455s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 11.812219381332397s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.7876622676849365s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.081031799316406e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.6689300537109375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 6.67572021484375e-06s
INFO | --- Analysis for datos-bcn-cl took 949.0804798603058s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.343721866607666s
Availability | VoID file availability check for datos.bne.es took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.2537980079650879s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011205673217773438s
Believability | Calculation of trust value for datos.bne.es took 8.106231689453125e-06s
INFO | --- Analysis for datos-bne-es took 6.209815263748169s
Availability | SPARQL endpoint availability check for DBkWik took 0.23385047912597656s
Availability | VoID file availability check for DBkWik took 0.0011887550354003906s
Extra | Recovery of all triples for DBkWik took 2.609767436981201s
Performance | Total latancy measurement for DBkWik took 0.4844090938568115s
Amount of data | Number of triples check for DBkWik took 4.112902641296387s
Interoperability | New terms check for DBkWik took 2.3502249717712402s
Versatility | Languages check for DBkWik took 62.9791738986969s
Interpretability | Number of blank nodes check for DBkWik took 0.1422586441040039s
Interpretability | RDF structures check for DBkWik took 0.38072896003723145s
Versatility | Serialization formats check for DBkWik took 0.18229436874389648s
Availability | RDF dump link check for DBkWik took 3.0045108795166016s
License | MR license check for DBkWik took 0.4329814910888672s
License | HR license check for DBkWik took 60.24808096885681s
Amount of data | Number of property check for DBkWik took 0.13245415687561035s
Understandability | Number of label check for DBkWik took 2.188152313232422s
Understandability | URI regex check for DBkWik took 0.2902703285217285s
Understandability | Vocabs check for DBkWik took 0.1412639617919922s
Verifiability | Authors check for DBkWik took 0.12057137489318848s
Verifiability | Publishers check for DBkWik took 0.11360812187194824s
Performance | Throughput check for DBkWik took 10.620692729949951s
Amount of data | Check the number of entities for DBkWik took 7.963180541992188e-05s
Verifiability | Contribs. check for DBkWik took 0.11789536476135254s
Interlinking | sameAs chians check for DBkWik took 0.3818826675415039s
Interlinking | skos check for DBkWik took 0.46836400032043457s
Interlinking | skos check for DBkWik took 0.09235811233520508s
Timeliness | dataset update frequency check for DBkWik took 0.20881223678588867s
Currency | Creation date check for DBkWik took 0.43895626068115234s
Currency | Modification date check for DBkWik took 0.19373583793640137s
Rep.Conc. | URIs length for DBkWik took 11.621316194534302s
Interoperability | New vocabularies check for DBkWik took 2.5922787189483643s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.11907482147216797s
Accuracy | Check Functional Property for DBkWik took 0.2834348678588867s
Accuracy | Check Inverse Functional Property for DBkWik took 0.2531399726867676s
Accuracy | Check Empty annotation labels for DBkWik took 0.9505553245544434s
Accuracy | Check White space in annotation for DBkWik took 0.023978710174560547s
Accuracy | Check Datatype consistency for DBkWik took 0.03751778602600098s
Consistency | Disjoint class check for DBkWik took 0.11009407043457031s
Consistency | Check Misplaced properties for DBkWik took 11.887614488601685s
Consistency | Misplaced classes for DBkWik took 0.6968095302581787s
Consistency | Check Ontology hijacking for DBkWik took 2.0666823387145996s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.3031301498413086s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.851064205169678s
Conciseness | Check Extensional conciseness for DBkWik took 0.03391766548156738s
Conciseness | Check Intensional conciseness for DBkWik took 0.9317905902862549s
Security | Sign check for DBkWik took 0.2563285827636719s
Availability | Check URIs Dereferenciability for DBkWik took 11.335379838943481s
Completeness | Calculation of interlinking completeness for DBkWik took 0.4325237274169922s
Reputation | Calculation of the PageRank for DBkWik took 0.1678638458251953s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for DBkWik took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 2.106227159500122s
Believability | Calculation of trust value for DBkWik took 9.775161743164062e-06s
INFO | --- Analysis for dbkwik took 1276.1715302467346s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 6.222724914550781e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.25398874282836914s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011348724365234375s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.4066696166992188e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 5.7116539478302s
Availability | SPARQL endpoint availability check for dbnary took 0.2521047592163086s
Availability | VoID file availability check for dbnary took 0.0005717277526855469s
Extra | Recovery of all triples for dbnary took 2.4052810668945312s
Performance | Total latancy measurement for dbnary took 0.36620497703552246s
Amount of data | Number of triples check for dbnary took 1.2363522052764893s
Interoperability | New terms check for dbnary took 3.6873178482055664s
Versatility | Languages check for dbnary took 61.98325729370117s
Interpretability | Number of blank nodes check for dbnary took 4.127029180526733s
Security | Check HTTPS for dbnary took 0.164201021194458s
Interpretability | RDF structures check for dbnary took 0.42147207260131836s
Versatility | Serialization formats check for dbnary took 0.9499132633209229s
Availability | RDF dump link check for dbnary took 0.06753706932067871s
License | MR license check for dbnary took 1.374471664428711s
License | HR license check for dbnary took 62.306461334228516s
Amount of data | Number of property check for dbnary took 0.10534286499023438s
Understandability | Number of label check for dbnary took 3.335275411605835s
Understandability | URI regex check for dbnary took 0.13924837112426758s
Understandability | Vocabs check for dbnary took 0.8383023738861084s
Verifiability | Authors check for dbnary took 0.9877636432647705s
Verifiability | Publishers check for dbnary took 0.3578834533691406s
Performance | Throughput check for dbnary took 10.267527341842651s
Amount of data | Check the number of entities for dbnary took 7.224082946777344e-05s
Verifiability | Contribs. check for dbnary took 0.43438148498535156s
Interlinking | sameAs chians check for dbnary took 0.10420083999633789s
Interlinking | skos check for dbnary took 0.8111159801483154s
Interlinking | skos check for dbnary took 0.07838964462280273s
Timeliness | dataset update frequency check for dbnary took 0.5286059379577637s
Currency | Creation date check for dbnary took 0.5662326812744141s
Currency | Modification date check for dbnary took 0.24944782257080078s
Rep.Conc. | URIs length for dbnary took 11.401742935180664s
Interoperability | New vocabularies check for dbnary took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.09087347984313965s
Accuracy | Check Functional Property for dbnary took 0.2675480842590332s
Accuracy | Check Inverse Functional Property for dbnary took 0.21463751792907715s
Accuracy | Check Empty annotation labels for dbnary took 1.7021842002868652s
Accuracy | Check White space in annotation for dbnary took 0.025990724563598633s
Accuracy | Check Datatype consistency for dbnary took 0.028606176376342773s
Consistency | Disjoint class check for dbnary took 0.22966790199279785s
Consistency | Check Misplaced properties for dbnary took 8.824987173080444s
Consistency | Misplaced classes for dbnary took 0.23913264274597168s
Consistency | Check Ontology hijacking for dbnary took 1.9195053577423096s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.3093829154968262s
Consistency | Check Invalid usage of undefined properties for dbnary took 9.995927810668945s
Conciseness | Check Extensional conciseness for dbnary took 0.037123680114746094s
Conciseness | Check Intensional conciseness for dbnary took 0.15315866470336914s
Security | Sign check for dbnary took 0.06546306610107422s
Availability | Check URIs Dereferenciability for dbnary took 10.433491706848145s
Completeness | Calculation of interlinking completeness for dbnary took 0.723705530166626s
Reputation | Calculation of the PageRank for dbnary took 0.021073341369628906s
Interlinking | Calculation of Degree of Connection for dbnary took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.430511474609375e-06s
Believability | Calculation of trust value for dbnary took 8.344650268554688e-06s
INFO | --- Analysis for dbnary took 314.0957748889923s
Availability | SPARQL endpoint availability check for DBpedia took 2.381223440170288s
Availability | VoID file availability check for DBpedia took 0.0005922317504882812s
Extra | Recovery of all triples for DBpedia took 3.644455909729004s
Performance | Total latancy measurement for DBpedia took 0.891925573348999s
Amount of data | Number of triples check for DBpedia took 1.5273387432098389s
Interoperability | New terms check for DBpedia took 5.551223278045654s
Versatility | Languages check for DBpedia took 31.757391929626465s
Interpretability | Number of blank nodes check for DBpedia took 0.17330288887023926s
Security | Check HTTPS for DBpedia took 0.13809919357299805s
Interpretability | RDF structures check for DBpedia took 0.27561116218566895s
Versatility | Serialization formats check for DBpedia took 0.26424646377563477s
Availability | RDF dump link check for DBpedia took 0.1676616668701172s
License | MR license check for DBpedia took 1.0035741329193115s
License | HR license check for DBpedia took 30.180747985839844s
Amount of data | Number of property check for DBpedia took 0.1793055534362793s
Understandability | Number of label check for DBpedia took 4.122792482376099s
Understandability | URI regex check for DBpedia took 0.6777105331420898s
Understandability | Vocabs check for DBpedia took 0.39508652687072754s
Verifiability | Authors check for DBpedia took 0.5439136028289795s
Verifiability | Publishers check for DBpedia took 0.21799993515014648s
Performance | Throughput check for DBpedia took 11.308818578720093s
Amount of data | Check the number of entities for DBpedia took 0.00017213821411132812s
Verifiability | Contribs. check for DBpedia took 0.3258507251739502s
Interlinking | sameAs chians check for DBpedia took 2.7633228302001953s
Interlinking | skos check for DBpedia took 6.683708190917969s
Interlinking | skos check for DBpedia took 0.18081450462341309s
Timeliness | dataset update frequency check for DBpedia took 0.19466185569763184s
Currency | Creation date check for DBpedia took 0.49942684173583984s
Currency | Modification date check for DBpedia took 0.46765995025634766s
Rep.Conc. | URIs length for DBpedia took 36.538580894470215s
Interoperability | New vocabularies check for DBpedia took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.2057044506072998s
Accuracy | Check Functional Property for DBpedia took 0.36373209953308105s
Accuracy | Check Inverse Functional Property for DBpedia took 0.27661871910095215s
Accuracy | Check Empty annotation labels for DBpedia took 3.7184898853302s
Accuracy | Check White space in annotation for DBpedia took 0.03058171272277832s
Accuracy | Check Datatype consistency for DBpedia took 0.02843618392944336s
Consistency | Disjoint class check for DBpedia took 0.27695155143737793s
Consistency | Check Misplaced properties for DBpedia took 31.965584993362427s
Consistency | Misplaced classes for DBpedia took 0.775442361831665s
Consistency | Check Ontology hijacking for DBpedia took 2.757744312286377s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.3316636085510254s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.6893970966339111s
Conciseness | Check Extensional conciseness for DBpedia took 0.03498411178588867s
Conciseness | Check Intensional conciseness for DBpedia took 4.544250726699829s
Security | Sign check for DBpedia took 0.19418001174926758s
Availability | Check URIs Dereferenciability for DBpedia took 6653.588789463043s
Completeness | Calculation of interlinking completeness for DBpedia took 0.692413330078125s
Reputation | Calculation of the PageRank for DBpedia took 0.025851726531982422s
Interlinking | Calculation of Degree of Connection for DBpedia took 9.274482727050781e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009396076202392578s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia took 7034.970165014267s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.155228853225708s
Availability | VoID file availability check for DBpedia Commons took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.7090158462524414s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.0208742618560791s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 7.2479248046875e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-commons took 17.17288088798523s
Availability | SPARQL endpoint availability check for DBpedia in German took 4.363059997558594e-05s
Availability | VoID file availability check for DBpedia in German took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.25104475021362305s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.508827209472656e-05s
Believability | Calculation of trust value for DBpedia in German took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia-de took 4.318379878997803s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 10.798121929168701s
Availability | VoID file availability check for DBpedia in Greek took 0.0007812976837158203s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.27716588973999023s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020876646041870117s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00020432472229003906s
Believability | Calculation of trust value for DBpedia in Greek took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-el took 46.29532313346863s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.43185925483703613s
Availability | VoID file availability check for DBpedia in Spanish took 0.00041294097900390625s
Extra | Recovery of all triples for DBpedia in Spanish took 2.495803117752075s
Performance | Total latancy measurement for DBpedia in Spanish took 1.6165616512298584s
Amount of data | Number of triples check for DBpedia in Spanish took 4.1417059898376465s
Interoperability | New terms check for DBpedia in Spanish took 2.8718676567077637s
Versatility | Languages check for DBpedia in Spanish took 61.53134107589722s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.42962026596069336s
Security | Check HTTPS for DBpedia in Spanish took 0.13992595672607422s
Interpretability | RDF structures check for DBpedia in Spanish took 0.9454069137573242s
Versatility | Serialization formats check for DBpedia in Spanish took 0.4753546714782715s
Availability | RDF dump link check for DBpedia in Spanish took 0.3948547840118408s
License | MR license check for DBpedia in Spanish took 0.7940764427185059s
License | HR license check for DBpedia in Spanish took 61.31376647949219s
Amount of data | Number of property check for DBpedia in Spanish took 0.3123457431793213s
Understandability | Number of label check for DBpedia in Spanish took 2.7689383029937744s
Understandability | URI regex check for DBpedia in Spanish took 0.8255987167358398s
Understandability | Vocabs check for DBpedia in Spanish took 0.39609360694885254s
Verifiability | Authors check for DBpedia in Spanish took 0.5912301540374756s
Verifiability | Publishers check for DBpedia in Spanish took 0.47834134101867676s
Performance | Throughput check for DBpedia in Spanish took 11.67743444442749s
Amount of data | Check the number of entities for DBpedia in Spanish took 0.00010943412780761719s
Verifiability | Contribs. check for DBpedia in Spanish took 0.6016292572021484s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.6265342235565186s
Interlinking | skos check for DBpedia in Spanish took 1.384580135345459s
Interlinking | skos check for DBpedia in Spanish took 0.23762822151184082s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.5231900215148926s
Currency | Creation date check for DBpedia in Spanish took 0.9715485572814941s
Currency | Modification date check for DBpedia in Spanish took 0.6755003929138184s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.517376899719238s
Interoperability | New vocabularies check for DBpedia in Spanish took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.3142073154449463s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.4054553508758545s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.444582462310791s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.3521411418914795s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.031049013137817383s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.02769184112548828s
Consistency | Disjoint class check for DBpedia in Spanish took 0.3305034637451172s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.14333438873291s
Consistency | Misplaced classes for DBpedia in Spanish took 1.9874906539916992s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.2979931831359863s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.3019323348999023s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 7.021366596221924s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03414559364318848s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.4598615169525146s
Security | Sign check for DBpedia in Spanish took 0.3259096145629883s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 11.16513204574585s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.2746601104736328s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00011444091796875s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-es took 637.5917975902557s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.1697311401367188s
Availability | VoID file availability check for DBpedia in Basque took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.6887350082397461s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.0040740966796875e-05s
Believability | Calculation of trust value for DBpedia in Basque took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-eu took 8.489270448684692s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.12996554374694824s
Availability | VoID file availability check for DBpedia in French took 0.0005581378936767578s
Extra | Recovery of all triples for DBpedia in French took 156.45732069015503s
Performance | Total latancy measurement for DBpedia in French took 0.41138601303100586s
Amount of data | Number of triples check for DBpedia in French took 1.6242523193359375s
Interoperability | New terms check for DBpedia in French took 2.3729419708251953s
Versatility | Languages check for DBpedia in French took 300.05137372016907s
Interpretability | Number of blank nodes check for DBpedia in French took 0.14167571067810059s
Interpretability | RDF structures check for DBpedia in French took 0.390794038772583s
Versatility | Serialization formats check for DBpedia in French took 0.31305718421936035s
Availability | RDF dump link check for DBpedia in French took 6.6169328689575195s
License | MR license check for DBpedia in French took 1.8678431510925293s
License | HR license check for DBpedia in French took 79.79490733146667s
Amount of data | Number of property check for DBpedia in French took 0.10637307167053223s
Understandability | Number of label check for DBpedia in French took 2.5935559272766113s
Understandability | URI regex check for DBpedia in French took 0.3028264045715332s
Understandability | Vocabs check for DBpedia in French took 0.12712740898132324s
Verifiability | Authors check for DBpedia in French took 0.4263482093811035s
Verifiability | Publishers check for DBpedia in French took 0.1746208667755127s
Performance | Throughput check for DBpedia in French took 10.56684684753418s
Amount of data | Check the number of entities for DBpedia in French took 2.1075706481933594s
Verifiability | Contribs. check for DBpedia in French took 0.19716858863830566s
Interlinking | sameAs chians check for DBpedia in French took 0.34731316566467285s
Interlinking | skos check for DBpedia in French took 0.23624253273010254s
Interlinking | skos check for DBpedia in French took 0.0755159854888916s
Timeliness | dataset update frequency check for DBpedia in French took 0.3055753707885742s
Currency | Creation date check for DBpedia in French took 0.2864854335784912s
Currency | Modification date check for DBpedia in French took 0.20030474662780762s
Rep.Conc. | URIs length for DBpedia in French took 66.40951466560364s
Interoperability | New vocabularies check for DBpedia in French took 8.534857749938965s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.10554695129394531s
Accuracy | Check Functional Property for DBpedia in French took 0.1843557357788086s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.14443111419677734s
Accuracy | Check Empty annotation labels for DBpedia in French took 47.10052180290222s
Accuracy | Check White space in annotation for DBpedia in French took 3.0958588123321533s
Accuracy | Check Datatype consistency for DBpedia in French took 2.735527992248535s
Consistency | Disjoint class check for DBpedia in French took 0.15571308135986328s
Consistency | Check Misplaced properties for DBpedia in French took 9.520174980163574s
Consistency | Misplaced classes for DBpedia in French took 9.73390793800354s
Consistency | Check Ontology hijacking for DBpedia in French took 54.16649079322815s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.418553352355957s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 9.913174390792847s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.0234012603759766s
Conciseness | Check Intensional conciseness for DBpedia in French took 2.116649866104126s
Security | Sign check for DBpedia in French took 0.12605834007263184s
Availability | Check URIs Dereferenciability for DBpedia in French took 1020.9831025600433s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.5130178928375244s
Reputation | Calculation of the PageRank for DBpedia in French took 0.0224153995513916s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00015306472778320312s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 7.7120201587677s
Believability | Calculation of trust value for DBpedia in French took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-fr took 1939.503033876419s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.8945302963256836s
Availability | VoID file availability check for DBpedia in Japanese took 4.148929595947266s
Extra | Recovery of all triples for DBpedia in Japanese took 8.550274133682251s
Performance | Total latancy measurement for DBpedia in Japanese took 6.644343376159668s
Amount of data | Number of triples check for DBpedia in Japanese took 92.91640996932983s
Interoperability | New terms check for DBpedia in Japanese took 22.272594928741455s
Versatility | Languages check for DBpedia in Japanese took 1.3543322086334229s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3453123569488525s
Security | Check HTTPS for DBpedia in Japanese took 0.811577320098877s
Interpretability | RDF structures check for DBpedia in Japanese took 1.7430477142333984s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3596134185791016s
Availability | RDF dump link check for DBpedia in Japanese took 1.3183584213256836s
License | MR license check for DBpedia in Japanese took 1.6920115947723389s
License | HR license check for DBpedia in Japanese took 92.71397161483765s
Amount of data | Number of property check for DBpedia in Japanese took 1.3563308715820312s
Understandability | Number of label check for DBpedia in Japanese took 13.618034839630127s
Understandability | URI regex check for DBpedia in Japanese took 2.69507098197937s
Understandability | Vocabs check for DBpedia in Japanese took 1.3316709995269775s
Verifiability | Authors check for DBpedia in Japanese took 1.34627366065979s
Verifiability | Publishers check for DBpedia in Japanese took 1.5827360153198242s
Performance | Throughput check for DBpedia in Japanese took 44.858967542648315s
Amount of data | Check the number of entities for DBpedia in Japanese took 7.05718994140625e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3460049629211426s
Interlinking | sameAs chians check for DBpedia in Japanese took 3.3135740756988525s
Interlinking | skos check for DBpedia in Japanese took 1.917959213256836s
Interlinking | skos check for DBpedia in Japanese took 1.345083236694336s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3456299304962158s
Currency | Creation date check for DBpedia in Japanese took 2.736621379852295s
Currency | Modification date check for DBpedia in Japanese took 2.7117831707000732s
Rep.Conc. | URIs length for DBpedia in Japanese took 111.87990927696228s
Interoperability | New vocabularies check for DBpedia in Japanese took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3668622970581055s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.4108026027679443s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.02568507194519043s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.029397249221801758s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4835484027862549s
Consistency | Check Misplaced properties for DBpedia in Japanese took 62.68185210227966s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 1.3168249130249023s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 2.858059883117676s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.033364295959472656s
Security | Sign check for DBpedia in Japanese took 1.3331637382507324s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 9.280476093292236s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.7444543838500977s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010323524475097656s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-ja took 959.126127243042s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.792213439941406e-05s
Availability | VoID file availability check for dbpedia lite took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.6920304298400879s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010061264038085938s
Believability | Calculation of trust value for dbpedia lite took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-lite took 4.216525077819824s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.2531273365020752s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.361701965332031e-05s
Believability | Calculation of trust value for DBpedia-Live took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-live took 3.760611057281494s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.23892688751220703s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2717916965484619s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001697540283203125s
Believability | Calculation of trust value for DBpedia in Dutch took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-nl took 3.175694465637207s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 4.988744735717773s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.26633739471435547s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.177757263183594e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-pt took 17.106307983398438s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.267692565917969e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.2723686695098877s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 2.9325485229492188e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-spotlight took 2.802093744277954s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 6.842613220214844e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.26247644424438477s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.818771362304688e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 6.67572021484375e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 14.044654607772827s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.124641418457031e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.2529914379119873s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02089691162109375s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.0517578125e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia-wikidata took 2.7757110595703125s
Availability | SPARQL endpoint availability check for DBpedia took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for DBpedia took 0.27060508728027344s
Reputation | Calculation of the PageRank for DBpedia took 0.020662546157836914s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.147125244140625e-05s
Believability | Calculation of trust value for DBpedia took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia_ took 2.885446548461914s
Availability | SPARQL endpoint availability check for DBTropes took 6.818771362304688e-05s
Availability | VoID file availability check for DBTropes took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for DBTropes took 0.25864744186401367s
Reputation | Calculation of the PageRank for DBTropes took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0008859634399414062s
Interlinking | Calculation of Clustering coefficient for DBTropes took 0.00010251998901367188s
Believability | Calculation of trust value for DBTropes took 9.5367431640625e-06s
INFO | --- Analysis for dbtropes took 3.3256123065948486s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.2438507080078125e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.2646157741546631s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020923137664794922s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.790855407714844e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 7.152557373046875e-06s
INFO | --- Analysis for dbtune took 2.8135430812835693s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.38690185546875e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2612001895904541s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.021097898483276367s
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.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.5789947509765625e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.2636184692382812e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 7.874823570251465s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.315376281738281e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.2704463005065918s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020830869674682617s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0008356571197509766s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.695487976074219e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.62939453125e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.880570650100708s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.935330390930176s
Availability | VoID file availability check for DBTune.org/classical took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.272735595703125s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.510185241699219e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-classical took 22.454766035079956s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.340700149536133s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2535734176635742s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020970821380615234s
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.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.796287536621094e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 5.9604644775390625e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 26.922685623168945s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.326576471328735s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.26894283294677734s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.021058320999145508s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.05718994140625e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 8.344650268554688e-06s
INFO | --- Analysis for dbtune-magnatune took 24.441092491149902s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.348036289215088s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.2858271598815918s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011229515075683594s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.89486837387085s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.330404996871948s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2633094787597656s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.340576171875e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-myspace took 17.876635313034058s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.291534423828125e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.263995885848999s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.02095961570739746s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.0517578125e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 8.344650268554688e-06s
INFO | --- Analysis for dclg-openuplabs took 2.8261666297912598s
Availability | SPARQL endpoint availability check for data.dcs took 4.3392181396484375e-05s
Availability | VoID file availability check for data.dcs took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for data.dcs took 0.26059556007385254s
Reputation | Calculation of the PageRank for data.dcs took 0.020690202713012695s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.508827209472656e-05s
Believability | Calculation of trust value for data.dcs took 8.58306884765625e-06s
INFO | --- Analysis for dcs-sheffield took 2.4345433712005615s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.5299530029296875e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.0003211498260498047s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.26878952980041504s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.170967102050781e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 8.821487426757812e-06s
INFO | --- Analysis for de-budget took 2.8229455947875977s
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.0007762908935546875s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2698557376861572s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.9577484130859375e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.152557373046875e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.297461986541748s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.3392181396484375e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.25660014152526855s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.0208890438079834s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.4345855712890625e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 8.58306884765625e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.3310747146606445s
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.0003898143768310547s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.25928163528442383s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.021898984909057617s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0011639595031738281s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.933906555175781e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 8.58306884765625e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.8346149921417236s
Availability | SPARQL endpoint availability check for Demografie took 5.14984130859375e-05s
Availability | VoID file availability check for Demografie took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Demografie took 0.25449585914611816s
Reputation | Calculation of the PageRank for Demografie took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for Demografie took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Demografie took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Demografie took 2.86102294921875e-05s
Believability | Calculation of trust value for Demografie took 7.62939453125e-06s
INFO | --- Analysis for demografie took 2.854008436203003s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.410743713378906e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.24630117416381836s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.655952453613281e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 9.059906005859375e-06s
INFO | --- Analysis for deustoentrepreneurship took 4.845918893814087s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.267692565917969e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0013761520385742188s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.26998043060302734s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020676136016845703s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0011081695556640625s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.0001239776611328125s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 2.0503997802734375e-05s
INFO | --- Analysis for deustotech took 5.517443895339966s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.4559717178344727s
Availability | VoID file availability check for Deutsche Biographie took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.24834966659545898s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020990848541259766s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.696846008300781e-05s
Believability | Calculation of trust value for Deutsche Biographie took 9.298324584960938e-06s
INFO | --- Analysis for deutsche-biographie took 4.217837333679199s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.8160552978515625e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.25545716285705566s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.650520324707031e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 6.67572021484375e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 4.059566020965576s
Availability | SPARQL endpoint availability check for dev8d took 4.601478576660156e-05s
Availability | VoID file availability check for dev8d took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for dev8d took 0.2554001808166504s
Reputation | Calculation of the PageRank for dev8d took 0.021069049835205078s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.961822509765625e-05s
Believability | Calculation of trust value for dev8d took 6.67572021484375e-06s
INFO | --- Analysis for dev8d took 2.8857264518737793s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.088316917419434s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0008032321929931641s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.26317501068115234s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.316734313964844e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 7.62939453125e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.46185493469238s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.38690185546875e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.27462244033813477s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.0279159545898438e-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.7970597743988037s
Availability | SPARQL endpoint availability check for Diavgeia took 4.267692565917969e-05s
Availability | VoID file availability check for Diavgeia took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.28393125534057617s
Reputation | Calculation of the PageRank for Diavgeia took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.463859558105469e-05s
Believability | Calculation of trust value for Diavgeia took 5.245208740234375e-06s
INFO | --- Analysis for diavgeia took 5.609142303466797s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.6253204345703125e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.2651481628417969s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02099156379699707s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00012183189392089844s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.58306884765625e-06s
INFO | --- Analysis for didactalia took 7.86881947517395s
Availability | SPARQL endpoint availability check for diigo.feed took 4.982948303222656e-05s
Availability | VoID file availability check for diigo.feed took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.2622354030609131s
Reputation | Calculation of the PageRank for diigo.feed took 0.02089405059814453s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 3.647804260253906e-05s
Believability | Calculation of trust value for diigo.feed took 9.775161743164062e-06s
INFO | --- Analysis for diigo-feed took 2.8301565647125244s
Availability | SPARQL endpoint availability check for DisGeNET took 0.338472843170166s
Availability | VoID file availability check for DisGeNET took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.2654151916503906s
Reputation | Calculation of the PageRank for DisGeNET took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015401840209960938s
Believability | Calculation of trust value for DisGeNET took 6.198883056640625e-06s
INFO | --- Analysis for disgenet took 3.226702928543091s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.26397061347961426s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.9802322387695312e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 6.67572021484375e-06s
INFO | --- Analysis for disk took 2.850761890411377s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.553794860839844e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.24596238136291504s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.02104783058166504s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0008234977722167969s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.361701965332031e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 7.867813110351562e-06s
INFO | --- Analysis for distritos-zaragoza took 2.839858293533325s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.506111145019531e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0007641315460205078s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2551872730255127s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0008122920989990234s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.218650817871094e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 9.775161743164062e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 10.407726287841797s
Availability | SPARQL endpoint availability check for DM2E took 4.410743713378906e-05s
Availability | VoID file availability check for DM2E took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for DM2E took 0.26846885681152344s
Reputation | Calculation of the PageRank for DM2E took 0.021266460418701172s
Interlinking | Calculation of Degree of Connection for DM2E took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0008931159973144531s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00012302398681640625s
Believability | Calculation of trust value for DM2E took 8.821487426757812e-06s
INFO | --- Analysis for dm2e took 3.2221627235412598s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.220008850097656e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.25171542167663574s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.0517578125e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.867813110351562e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.9262092113494873s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.8370099067687988s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.31969332695007324s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001537799835205078s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 8.821487426757812e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 8.99828052520752s
Availability | SPARQL endpoint availability check for DOAP Store took 0.00013303756713867188s
Availability | VoID file availability check for DOAP Store took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.2738606929779053s
Reputation | Calculation of the PageRank for DOAP Store took 0.020899534225463867s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.075599670410156e-05s
Believability | Calculation of trust value for DOAP Store took 1.811981201171875e-05s
INFO | --- Analysis for doap_store took 2.8674681186676025s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.2438507080078125e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0003762245178222656s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.2445077896118164s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.198883056640625e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.245208740234375e-06s
INFO | --- Analysis for doi took 7.3029539585113525s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 6.175199031829834s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0007653236389160156s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.25212669372558594s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.743171691894531e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 7.867813110351562e-06s
INFO | --- Analysis for drug-data-hifm took 35.83250570297241s
Availability | SPARQL endpoint availability check for dspace took 4.220008850097656e-05s
Availability | VoID file availability check for dspace took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for dspace took 0.2523338794708252s
Reputation | Calculation of the PageRank for dspace took 0.020951271057128906s
Interlinking | Calculation of Degree of Connection for dspace took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for dspace took 3.24249267578125e-05s
Believability | Calculation of trust value for dspace took 6.9141387939453125e-06s
INFO | --- Analysis for dspace took 2.865422487258911s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.220008850097656e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.26325440406799316s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 6.67572021484375e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.846607208251953s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 270.389803647995s
Availability | VoID file availability check for MetaLex Document Server took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.2409508228302002s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.021285533905029297s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 4.76837158203125e-05s
Believability | Calculation of trust value for MetaLex Document Server took 6.67572021484375e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 553.6938829421997s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 5.942771911621094s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.2441561222076416s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020708084106445312s
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.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.719329833984375e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 8.106231689453125e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 15.158016681671143s
Availability | SPARQL endpoint availability check for DWS-Group took 4.38690185546875e-05s
Availability | VoID file availability check for DWS-Group took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.2402040958404541s
Reputation | Calculation of the PageRank for DWS-Group took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010585784912109375s
Believability | Calculation of trust value for DWS-Group took 3.266334533691406e-05s
INFO | --- Analysis for dws-group took 2.528195381164551s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.050444841384887695s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.23873567581176758s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020449161529541016s
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.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011658668518066406s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-alaska took 2.7801055908203125s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.02967524528503418s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.24796080589294434s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.2928924560546875e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-cau took 2.3502724170684814s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.032854318618774414s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2473437786102295s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.437301635742188e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 3.265913724899292s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.04295158386230469s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0003879070281982422s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.258197546005249s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.34600830078125e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.8195481300354004s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.023061037063598633s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.2566101551055908s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00016999244689941406s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.3136696815490723s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.03324389457702637s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.26598525047302246s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02098870277404785s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 9.179115295410156e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-famu took 2.467250347137451s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.018801212310791016s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.25411200523376465s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013208389282226562s
Believability | Calculation of trust value for eagle-i @ Harvard University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-harvard took 2.3623814582824707s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0294344425201416s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2593119144439697s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020762920379638672s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012612342834472656s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.3519372940063477s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.02987957000732422s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00021147727966308594s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2671661376953125s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.29425048828125e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 5.7220458984375e-06s
INFO | --- Analysis for eagle-i-howard took 2.363264322280884s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.05997323989868164s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0003859996795654297s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2547342777252197s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.02108621597290039s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.3940622806549072s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.037058115005493164s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00021147727966308594s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.245635986328125s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00010943412780761719s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-jsu took 2.367133140563965s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.033712148666381836s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.2570009231567383s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.0209503173828125s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.9577484130859375e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-meharry took 2.351985216140747s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.03271842002868652s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.00020122528076171875s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.24558520317077637s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02080368995666504s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.465217590332031e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-montana took 2.2952635288238525s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.03378438949584961s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.24931836128234863s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.369850158691406e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 5.245208740234375e-06s
INFO | --- Analysis for eagle-i-msm took 2.333923816680908s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.037004947662353516s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00020456314086914062s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.26633715629577637s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020910263061523438s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00015306472778320312s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.4057047367095947s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.03757953643798828s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2582576274871826s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.532669067382812e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 5.9604644775390625e-06s
INFO | --- Analysis for eagle-i-psm took 2.383262872695923s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.029434919357299805s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.00021505355834960938s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.23912668228149414s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.02105855941772461s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.29425048828125e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-tsu took 2.3336238861083984s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.032913923263549805s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0001995563507080078s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2689032554626465s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.365776062011719e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.3643479347229004s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.02350163459777832s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00020313262939453125s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.26654958724975586s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02099466323852539s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.72747802734375e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 5.9604644775390625e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.3395845890045166s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.036386966705322266s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.26423072814941406s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.021488189697265625s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00013518333435058594s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-upr took 2.451207160949707s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.04681682586669922s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.25725460052490234s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.270408630371094e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-utep took 2.410439968109131s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.025243043899536133s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0003826618194580078s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.263195276260376s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.319450378417969e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 9.5367431640625e-06s
INFO | --- Analysis for eagle-i-utsa took 2.350644111633301s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.17411184310913086s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.26473164558410645s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.5367431640625e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.4873461723327637s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.037156105041503906s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.260394811630249s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020693063735961914s
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.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.748603820800781e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-xula took 2.4150514602661133s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.35681724548339844s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2417011260986328s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.02113056182861328s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010561943054199219s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for ecb-linked-data took 2.6822359561920166s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 0.1469416618347168s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.24271345138549805s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.62396240234375e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.7220458984375e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 2.5616657733917236s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.5110986232757568s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.26113343238830566s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.747245788574219e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 5.498033285140991s
Availability | SPARQL endpoint availability check for ECLAP took 20.496249437332153s
Availability | VoID file availability check for ECLAP took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for ECLAP took 0.2484142780303955s
Reputation | Calculation of the PageRank for ECLAP took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.6716461181640625e-05s
Believability | Calculation of trust value for ECLAP took 8.58306884765625e-06s
INFO | --- Analysis for eclap took 52.94862604141235s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.839897155761719e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.26778483390808105s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02055525779724121s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.364418029785156e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 6.9141387939453125e-06s
INFO | --- Analysis for ecs took 2.3353066444396973s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.291534423828125e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.26325225830078125s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 2.956390380859375e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 6.67572021484375e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.7765607833862305s
Availability | SPARQL endpoint availability check for Edublogs took 4.553794860839844e-05s
Availability | VoID file availability check for Edublogs took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Edublogs took 0.25316381454467773s
Reputation | Calculation of the PageRank for Edublogs took 0.02051401138305664s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.0001010894775390625s
Believability | Calculation of trust value for Edublogs took 7.62939453125e-06s
INFO | --- Analysis for edublogs took 3.63356351852417s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.30463719367980957s
Availability | VoID file availability check for education.data.gov.uk took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.2676551342010498s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.749961853027344e-05s
Believability | Calculation of trust value for education.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for education-data-gov-uk took 4.016354322433472s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.26826000213623047s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.3909759521484375e-06s
INFO | --- Analysis for education-openuplabs took 2.8658082485198975s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 393.38255882263184s
Availability | VoID file availability check for Educational programs - SISVU took 0.0011730194091796875s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.8558220863342285s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.022480249404907227s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.5789947509765625e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 8.344650268554688e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1323.6853203773499s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.9746735095977783s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.6810956001281738s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.363059997558594e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.4836273193359375e-06s
INFO | --- Analysis for eea took 13.189885139465332s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.4009263515472412s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.001134634017944336s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.2546381950378418s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020540475845336914s
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.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.14984130859375e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 6.4373016357421875e-06s
INFO | --- Analysis for eea-rod took 5.524813413619995s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.16377758979797363s
Availability | VoID file availability check for EEA Vocabularies took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.25882625579833984s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020792484283447266s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0009670257568359375s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 0.0001010894775390625s
Believability | Calculation of trust value for EEA Vocabularies took 8.344650268554688e-06s
INFO | --- Analysis for eea-vocabularies took 5.039180755615234s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 9.131431579589844e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.2408292293548584s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020676136016845703s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for ege-university-linked-open-data took 3.352067708969116s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.410743713378906e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.25106167793273926s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010442733764648438s
Believability | Calculation of trust value for EIONET RDF Data took 8.106231689453125e-06s
INFO | --- Analysis for eionet-rdf took 2.591510534286499s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 7.843971252441406e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.25174951553344727s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.9325485229492188e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.62939453125e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 2.8630406856536865s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.236433744430542s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.2753255367279053s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 9.751319885253906e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.0251998901367188e-05s
INFO | --- Analysis for elviajero took 19.111196756362915s
Availability | SPARQL endpoint availability check for EMN took 4.482269287109375e-05s
Availability | VoID file availability check for EMN took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for EMN took 0.26201963424682617s
Reputation | Calculation of the PageRank for EMN took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for EMN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for EMN took 3.9577484130859375e-05s
Believability | Calculation of trust value for EMN took 7.867813110351562e-06s
INFO | --- Analysis for emn took 2.7111990451812744s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.4345855712890625e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.26671695709228516s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02097034454345703s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0010256767272949219s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 6.008148193359375e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-co2emission took 2.454773187637329s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.25862765312194824s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.021215438842773438s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.38690185546875e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 6.198883056640625e-06s
INFO | --- Analysis for enakting-crime took 2.356931447982788s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.506111145019531e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2506589889526367s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.022613525390625s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0011172294616699219s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 5.054473876953125e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for enakting-energy took 2.3061819076538086s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.4345855712890625e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00054931640625s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.2653367519378662s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.02090620994567871s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 0.00010013580322265625s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for enakting-mortality took 2.3388185501098633s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.506111145019531e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.2552957534790039s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.790855407714844e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for enakting-nhs took 2.363546848297119s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 6.318092346191406e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.25543761253356934s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.459785461425781e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for enakting-population took 2.302248954772949s
Availability | SPARQL endpoint availability check for Enel Shops took 5.269050598144531e-05s
Availability | VoID file availability check for Enel Shops took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.27339816093444824s
Reputation | Calculation of the PageRank for Enel Shops took 0.02081918716430664s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.2901763916015625e-05s
Believability | Calculation of trust value for Enel Shops took 8.821487426757812e-06s
INFO | --- Analysis for enel-shops took 2.9080638885498047s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.9114227294921875e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.24477148056030273s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020745515823364258s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 4.029273986816406e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 8.344650268554688e-06s
INFO | --- Analysis for energy-efficiency took 2.842594623565674s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.2683093547821045s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.021091699600219727s
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.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.266334533691406e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.8449923992156982s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2788238525390625s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 2.8133392333984375e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.864856004714966s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.3392181396484375e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.26296019554138184s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020956039428710938s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.885319471359253s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.2659745216369629s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.021226167678833008s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0010230541229248047s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.981590270996094e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.8363420963287354s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 5.841255187988281e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00039696693420410156s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.2587709426879883s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.021193265914916992s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007927417755126953s
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 8.344650268554688e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.831984519958496s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.27197861671447754s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020787954330444336s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.361701965332031e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.9268999099731445s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 5.602836608886719e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.23937678337097168s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 9.5367431640625e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.889937400817871s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.7681305408477783s
Availability | VoID file availability check for English Heritage Periods List took 0.0007891654968261719s
Extra | Recovery of all triples for English Heritage Periods List took 0.4441401958465576s
Performance | Total latancy measurement for English Heritage Periods List took 2.0187673568725586s
Amount of data | Number of triples check for English Heritage Periods List took 1.5626590251922607s
Versatility | Languages check for English Heritage Periods List took 0.3606705665588379s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5965254306793213s
Security | Check HTTPS for English Heritage Periods List took 0.2673680782318115s
Interpretability | RDF structures check for English Heritage Periods List took 0.35779452323913574s
Versatility | Serialization formats check for English Heritage Periods List took 0.49417710304260254s
Availability | RDF dump link check for English Heritage Periods List took 0.4058821201324463s
License | MR license check for English Heritage Periods List took 1.5764496326446533s
License | HR license check for English Heritage Periods List took 0.4368569850921631s
Amount of data | Number of property check for English Heritage Periods List took 0.4671440124511719s
Understandability | Number of label check for English Heritage Periods List took 0.5662679672241211s
Understandability | URI regex check for English Heritage Periods List took 0.7586028575897217s
Understandability | Vocabs check for English Heritage Periods List took 0.47087931632995605s
Verifiability | Authors check for English Heritage Periods List took 0.4982738494873047s
Verifiability | Publishers check for English Heritage Periods List took 0.4127202033996582s
Performance | Throughput check for English Heritage Periods List took 11.859906196594238s
Amount of data | Check the number of entities for English Heritage Periods List took 7.271766662597656e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.42116665840148926s
Interlinking | sameAs chians check for English Heritage Periods List took 0.3818786144256592s
Interlinking | skos check for English Heritage Periods List took 0.4249720573425293s
Interlinking | skos check for English Heritage Periods List took 0.4210379123687744s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.5717730522155762s
Currency | Creation date check for English Heritage Periods List took 0.8026783466339111s
Currency | Modification date check for English Heritage Periods List took 0.8574256896972656s
Rep.Conc. | URIs length for English Heritage Periods List took 0.7815515995025635s
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.4021332263946533s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3979787826538086s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.395430326461792s
Consistency | Disjoint class check for English Heritage Periods List took 0.39314842224121094s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.4097895622253418s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.7237613201141357s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0004792213439941406s
Security | Sign check for English Heritage Periods List took 0.39863133430480957s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.2652602195739746s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.504753112792969e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 1.5020370483398438e-05s
INFO | --- Analysis for english-heritage-periods-list took 61.58991599082947s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.6146881580352783s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0007548332214355469s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 0.231306791305542s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 0.8870248794555664s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.26495838165283203s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 2.1113874912261963s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.3150177001953125s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 0.2884552478790283s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.17746353149414062s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.2592182159423828s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.19706177711486816s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 50.40089821815491s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 1.2886145114898682s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 0.31406617164611816s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.2160015106201172s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.29469752311706543s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.27643489837646484s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.1438002586364746s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.16330409049987793s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.2897000312805176s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 12.124150276184082s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 6.747245788574219e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.1789846420288086s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.3089914321899414s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.3377339839935303s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.16028785705566406s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.12686562538146973s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.534625768661499s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.317401647567749s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 0.7234542369842529s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.16384577751159668s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.2306966781616211s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.14402532577514648s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.44665050506591797s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 1.6094365119934082s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 0.2937204837799072s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.5819017887115479s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.00016999244689941406s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.4620063304901123s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.142333984375s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.2662220001220703s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02183365821838379s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0010275840759277344s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 4.267692565917969e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 6.198883056640625e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 179.68729209899902s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.15747761726379395s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0007925033569335938s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 0.24889779090881348s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.7330634593963623s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.1436779499053955s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.551288366317749s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.21229028701782227s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 0.21580219268798828s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.11514472961425781s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.2178952693939209s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.15473222732543945s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 44.73735857009888s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.19719958305358887s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 0.2874417304992676s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.21991682052612305s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.15953302383422852s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.34871768951416016s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.14843201637268066s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.200791597366333s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.1445906162261963s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 12.048768758773804s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 0.00016045570373535156s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.22203326225280762s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.1493990421295166s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.13781952857971191s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.14705681800842285s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.14815855026245117s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.28496217727661133s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.160186767578125s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 0.42252469062805176s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.14508056640625s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.13546276092529297s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.18632078170776367s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.14864826202392578s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.9337761402130127s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 0.21338725090026855s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.5653102397918701s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00014162063598632812s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.24252915382385254s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.13341116905212402s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.252453088760376s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.3855438232421875e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.0067901611328125e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 162.0629529953003s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.3392181396484375e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.6945335865020752s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.0517578125e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 8.58306884765625e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 3.6931726932525635s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.291534423828125e-05s
Availability | VoID file availability check for English Heritage Places took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.25446534156799316s
Reputation | Calculation of the PageRank for English Heritage Places took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 2.9325485229492188e-05s
Believability | Calculation of trust value for English Heritage Places took 6.198883056640625e-06s
INFO | --- Analysis for englishheritage_places took 2.7783262729644775s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.1318814754486084s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00040030479431152344s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.25670695304870605s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.250640869140625e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 8.106231689453125e-06s
INFO | --- Analysis for enipedia took 2.4849162101745605s
Availability | SPARQL endpoint availability check for Entrez Gene took 7.224082946777344e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008296966552734375s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2634704113006592s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02087116241455078s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.62396240234375e-05s
Believability | Calculation of trust value for Entrez Gene took 6.9141387939453125e-06s
INFO | --- Analysis for entrez_gene took 27.41765284538269s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.363059997558594e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.2708590030670166s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.314018249511719e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.62939453125e-06s
INFO | --- Analysis for entrez_gene_extract took 2.8487563133239746s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0428688526153564s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.24600839614868164s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 4.839897155761719e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 6.4373016357421875e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 11.415709495544434s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.31493592262268066s
Availability | VoID file availability check for environment.data.gov.uk took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.2476496696472168s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.649162292480469e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.063661336898804s
Availability | SPARQL endpoint availability check for EARTh took 272.13340187072754s
Availability | VoID file availability check for EARTh took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for EARTh took 0.26514339447021484s
Reputation | Calculation of the PageRank for EARTh took 0.020917415618896484s
Interlinking | Calculation of Degree of Connection for EARTh took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00011610984802246094s
Believability | Calculation of trust value for EARTh took 7.3909759521484375e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 563.6618781089783s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.76837158203125e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.27036547660827637s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.4332275390625e-05s
Believability | Calculation of trust value for EPA-CDR took 5.4836273193359375e-06s
INFO | --- Analysis for epa-cdr took 10.394547462463379s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-FRS took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.27193331718444824s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.319450378417969e-05s
Believability | Calculation of trust value for EPA-FRS took 5.245208740234375e-06s
INFO | --- Analysis for epa-frs took 6.1136534214019775s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.25548815727233887s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.24249267578125e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.0067901611328125e-06s
INFO | --- Analysis for epa-rcra took 6.045067071914673s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.792213439941406e-05s
Availability | VoID file availability check for EPA-SRS took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.2493913173675537s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020939111709594727s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0008828639984130859s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 8.654594421386719e-05s
Believability | Calculation of trust value for EPA-SRS took 5.9604644775390625e-06s
INFO | --- Analysis for epa-srs took 6.070859670639038s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.38690185546875e-05s
Availability | VoID file availability check for EPA-TRI took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.26772546768188477s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.075599670410156e-05s
Believability | Calculation of trust value for EPA-TRI took 5.245208740234375e-06s
INFO | --- Analysis for epa-tri took 5.728340148925781s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.1961669921875e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.24828219413757324s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.557868957519531e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 6.4373016357421875e-06s
INFO | --- Analysis for epo took 2.781982183456421s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.03557133674621582s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.00036525726318359375s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.2664182186126709s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.0220639705657959s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0008220672607421875s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00014519691467285156s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.391406297683716s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.3820364475250244s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.26976442337036133s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020662546157836914s
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.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.177757263183594e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 6.9141387939453125e-06s
INFO | --- Analysis for eprtr took 3.282937526702881s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.1451869010925293s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2596292495727539s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.075599670410156e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 5.4836273193359375e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.662389039993286s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.410743713378906e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2705364227294922s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.893013000488281e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 5.245208740234375e-06s
INFO | --- Analysis for esd-standards took 3.8185441493988037s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.458427429199219e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.2615516185760498s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.176399230957031e-05s
Believability | Calculation of trust value for ESD-Toolkit took 5.245208740234375e-06s
INFO | --- Analysis for esd-toolkit took 3.0136568546295166s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 0.13599133491516113s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2588329315185547s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 8.344650268554688e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 6.67572021484375e-06s
INFO | --- Analysis for eu-agencies-bodies took 2.600891351699829s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 4.506111145019531e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.26194262504577637s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.1948089599609375e-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.7988803386688232s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.315376281738281e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.25702977180480957s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.02056407928466797s
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.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.367134094238281e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 4.291534423828125e-06s
INFO | --- Analysis for eu-institutions took 2.443621873855591s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.07183456420898438s
Availability | VoID file availability check for EU Parliament Media Library took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.26852846145629883s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.170967102050781e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.4836273193359375e-06s
INFO | --- Analysis for eu-parliament-media took 2.436953067779541s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.05855822563171387s
Availability | VoID file availability check for EU Who Is Who took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.24365544319152832s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.504753112792969e-05s
Believability | Calculation of trust value for EU Who Is Who took 5.245208740234375e-06s
INFO | --- Analysis for eu-who-is-who took 2.4209342002868652s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.04618358612060547s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0003867149353027344s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.2583034038543701s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.910064697265625e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for eumida-linked-data took 2.455559253692627s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.22169709205627441s
Availability | VoID file availability check for European Nature Information System took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.26035022735595703s
Reputation | Calculation of the PageRank for European Nature Information System took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010538101196289062s
Believability | Calculation of trust value for European Nature Information System took 6.67572021484375e-06s
INFO | --- Analysis for eunis took 4.047574996948242s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 0.12731361389160156s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.24247026443481445s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.200241088867188e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for eur-lex-rdf took 2.551168203353882s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.056293487548828125s
Availability | VoID file availability check for Standard Eurobarometer took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2567150592803955s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.100799560546875e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 5.245208740234375e-06s
INFO | --- Analysis for eurobarometer-standard took 2.5616848468780518s
Availability | SPARQL endpoint availability check for European Election Results took 0.05624818801879883s
Availability | VoID file availability check for European Election Results took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for European Election Results took 0.25498485565185547s
Reputation | Calculation of the PageRank for European Election Results took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.3855438232421875e-05s
Believability | Calculation of trust value for European Election Results took 5.0067901611328125e-06s
INFO | --- Analysis for european-election-results took 2.536599636077881s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.267692565917969e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.24942922592163086s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for europeana-lod took 2.790778636932373s
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.0011785030364990234s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.28951001167297363s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.1552734375e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.3909759521484375e-06s
INFO | --- Analysis for europeana-lod-v1 took 7.072817325592041s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.017048358917236328s
Availability | VoID file availability check for Europeana SPARQL took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.2690107822418213s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020696640014648438s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.57763671875e-05s
Believability | Calculation of trust value for Europeana SPARQL took 7.152557373046875e-06s
INFO | --- Analysis for europeana-sparql took 2.488819122314453s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07304692268371582s
Availability | VoID file availability check for EuroSentiment took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.28644776344299316s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.719329833984375e-05s
Believability | Calculation of trust value for EuroSentiment took 8.106231689453125e-06s
INFO | --- Analysis for eurosentiment took 3.029834270477295s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.267692565917969e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.00035834312438964844s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.2509117126464844s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.440017700195312e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 4.5299530029296875e-06s
INFO | --- Analysis for eurostat-rdf took 12.264649629592896s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.124641418457031e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0008511543273925781s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.25484752655029297s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 3.719329833984375e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 8.344650268554688e-06s
INFO | --- Analysis for eurovoc-in-skos took 2.8117153644561768s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.1484832763671875e-05s
Availability | VoID file availability check for European Television Heritage took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.25284862518310547s
Reputation | Calculation of the PageRank for European Television Heritage took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.8133392333984375e-05s
Believability | Calculation of trust value for European Television Heritage took 1.1205673217773438e-05s
INFO | --- Analysis for euscreen took 2.802104949951172s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 5.555152893066406e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.26690077781677246s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 5.3882598876953125e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 5.245208740234375e-06s
INFO | --- Analysis for euskadi-farmacias took 4.939840793609619s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.3201782703399658s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0007731914520263672s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2686896324157715s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.021162986755371094s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.176399230957031e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 8.344650268554688e-06s
INFO | --- Analysis for eutc-productions took 9.685840606689453s
Availability | SPARQL endpoint availability check for EventMedia took 0.2955739498138428s
Availability | VoID file availability check for EventMedia took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for EventMedia took 0.2726716995239258s
Reputation | Calculation of the PageRank for EventMedia took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010657310485839844s
Believability | Calculation of trust value for EventMedia took 7.62939453125e-06s
INFO | --- Analysis for event-media took 14.116182565689087s
Availability | SPARQL endpoint availability check for Eventseer took 1.677121639251709s
Availability | VoID file availability check for Eventseer took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2585113048553467s
Reputation | Calculation of the PageRank for Eventseer took 0.0205996036529541s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.6253204345703125e-05s
Believability | Calculation of trust value for Eventseer took 8.821487426757812e-06s
INFO | --- Analysis for eventseer took 3.983461856842041s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.2438507080078125e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.2593803405761719s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 2.9325485229492188e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 8.106231689453125e-06s
INFO | --- Analysis for facebook-lids took 2.776108503341675s
Availability | SPARQL endpoint availability check for Fact Forge took 4.172325134277344e-05s
Availability | VoID file availability check for Fact Forge took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.2609734535217285s
Reputation | Calculation of the PageRank for Fact Forge took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 2.8133392333984375e-05s
Believability | Calculation of trust value for Fact Forge took 8.106231689453125e-06s
INFO | --- Analysis for fact-forge took 2.8993163108825684s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.38690185546875e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.2658665180206299s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010061264038085938s
Believability | Calculation of trust value for FAO geopolitical ontology took 4.76837158203125e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.65545392036438s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.13599205017089844s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.2673921585083008s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010776519775390625s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for fao-linked-data took 2.453745126724243s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.516652584075928s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0007946491241455078s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2560160160064697s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.021068334579467773s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0010480880737304688s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 5.245208740234375e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 8.821487426757812e-06s
INFO | --- Analysis for farmbio-chembl took 63.957953453063965s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.1961669921875e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.25798797607421875s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.0517578125e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 7.867813110351562e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 2.8663887977600098s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.482269287109375e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.25261926651000977s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.409385681152344e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for farolapp-dataset took 2.886857748031616s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.1484832763671875e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.2638237476348877s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007503032684326172s
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.3909759521484375e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.8592894077301025s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 6.794929504394531e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.24820852279663086s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.0994415283203125e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 5.9604644775390625e-06s
INFO | --- Analysis for federal-economic-rdf took 2.8177573680877686s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.2438507080078125e-05s
Availability | VoID file availability check for Feed Wrapper took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.25713038444519043s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.020679950714111328s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.0994415283203125e-05s
Believability | Calculation of trust value for Feed Wrapper took 7.152557373046875e-06s
INFO | --- Analysis for feedwrapper-lids took 2.8207693099975586s
Availability | SPARQL endpoint availability check for FiESTA took 4.315376281738281e-05s
Availability | VoID file availability check for FiESTA took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for FiESTA took 0.2843313217163086s
Reputation | Calculation of the PageRank for FiESTA took 0.02414250373840332s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0015578269958496094s
Interlinking | Calculation of Clustering coefficient for FiESTA took 6.365776062011719e-05s
Believability | Calculation of trust value for FiESTA took 7.867813110351562e-06s
INFO | --- Analysis for fiesta took 12.505787372589111s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.57763671875e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2553141117095947s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.05718994140625e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.7220458984375e-06s
INFO | --- Analysis for finnish-municipalities took 6.050235033035278s
Availability | SPARQL endpoint availability check for firmao took 4.291534423828125e-05s
Availability | VoID file availability check for firmao took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for firmao took 0.24143648147583008s
Reputation | Calculation of the PageRank for firmao took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for firmao took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for firmao took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for firmao took 3.0279159545898438e-05s
Believability | Calculation of trust value for firmao took 7.62939453125e-06s
INFO | --- Analysis for firmao took 2.7260537147521973s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.2416226863861084s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.796525001525879s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.363059997558594e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.23987507820129395s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.00098419189453125s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 0.00010204315185546875s
Believability | Calculation of trust value for Fishes of Texas took 7.3909759521484375e-06s
INFO | --- Analysis for fishes-of-texas took 2.765479326248169s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.3392181396484375e-05s
Availability | VoID file availability check for flickr? wrappr took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.25130772590637207s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.34600830078125e-05s
Believability | Calculation of trust value for flickr? wrappr took 7.3909759521484375e-06s
INFO | --- Analysis for flickr-wrappr took 3.26308012008667s
Availability | SPARQL endpoint availability check for flickr.person took 4.38690185546875e-05s
Availability | VoID file availability check for flickr.person took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for flickr.person took 0.24393105506896973s
Reputation | Calculation of the PageRank for flickr.person took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0008289813995361328s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.218650817871094e-05s
Believability | Calculation of trust value for flickr.person took 6.4373016357421875e-06s
INFO | --- Analysis for flickr_person took 2.812065362930298s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.1484832763671875e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.26560449600219727s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 2.9802322387695312e-05s
Believability | Calculation of trust value for flickr.videoobject took 9.775161743164062e-06s
INFO | --- Analysis for flickr_videoobject took 2.7538602352142334s
Availability | SPARQL endpoint availability check for Fly-TED took 4.1484832763671875e-05s
Availability | VoID file availability check for Fly-TED took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.25833868980407715s
Reputation | Calculation of the PageRank for Fly-TED took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 2.8133392333984375e-05s
Believability | Calculation of trust value for Fly-TED took 3.170967102050781e-05s
INFO | --- Analysis for fly-ted took 2.762500762939453s
Availability | SPARQL endpoint availability check for FlyAtlas took 4.1961669921875e-05s
Availability | VoID file availability check for FlyAtlas took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.269946813583374s
Reputation | Calculation of the PageRank for FlyAtlas took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.0040740966796875e-05s
Believability | Calculation of trust value for FlyAtlas took 8.106231689453125e-06s
INFO | --- Analysis for flyatlas took 2.9026100635528564s
Availability | SPARQL endpoint availability check for Flybase took 1.5422229766845703s
Availability | VoID file availability check for Flybase took 0.0003788471221923828s
Completeness | Calculation of interlinking completeness for Flybase took 0.2381131649017334s
Reputation | Calculation of the PageRank for Flybase took 0.020862579345703125s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.695487976074219e-05s
Believability | Calculation of trust value for Flybase took 8.58306884765625e-06s
INFO | --- Analysis for flybase took 9.407650232315063s
Availability | SPARQL endpoint availability check for Flyted took 1.3722782135009766s
Availability | VoID file availability check for Flyted took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Flyted took 0.2690622806549072s
Reputation | Calculation of the PageRank for Flyted took 0.020796775817871094s
Interlinking | Calculation of Degree of Connection for Flyted took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0009491443634033203s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.218650817871094e-05s
Believability | Calculation of trust value for Flyted took 7.62939453125e-06s
INFO | --- Analysis for flyted took 10.621865510940552s
Availability | SPARQL endpoint availability check for Foodista took 0.7945449352264404s
Availability | VoID file availability check for Foodista took 0.0007104873657226562s
Completeness | Calculation of interlinking completeness for Foodista took 0.25586771965026855s
Reputation | Calculation of the PageRank for Foodista took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9802322387695312e-05s
Believability | Calculation of trust value for Foodista took 7.62939453125e-06s
INFO | --- Analysis for foodista took 9.46799373626709s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2679109573364258s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2551567554473877s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.009506225585938e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.049041748046875e-05s
INFO | --- Analysis for foodpedia took 2.633821964263916s
Availability | SPARQL endpoint availability check for FORGE Course information took 5.1975250244140625e-05s
Availability | VoID file availability check for FORGE Course information took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.255124568939209s
Reputation | Calculation of the PageRank for FORGE Course information took 0.02103734016418457s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.123283386230469e-05s
Believability | Calculation of trust value for FORGE Course information took 6.9141387939453125e-06s
INFO | --- Analysis for forge-course-information took 2.8270957469940186s
Availability | SPARQL endpoint availability check for FrameNet took 4.2438507080078125e-05s
Availability | VoID file availability check for FrameNet took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for FrameNet took 0.2612578868865967s
Reputation | Calculation of the PageRank for FrameNet took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for FrameNet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FrameNet took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for FrameNet took 2.8371810913085938e-05s
Believability | Calculation of trust value for FrameNet took 7.152557373046875e-06s
INFO | --- Analysis for framenet took 2.8293304443359375s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.15897321701049805s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.23792815208435059s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.320808410644531e-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.4542932510375977s
Availability | SPARQL endpoint availability check for Freebase took 4.410743713378906e-05s
Availability | VoID file availability check for Freebase took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Freebase took 0.2501101493835449s
Reputation | Calculation of the PageRank for Freebase took 0.020789384841918945s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00028133392333984375s
Believability | Calculation of trust value for Freebase took 1.2874603271484375e-05s
INFO | --- Analysis for freebase took 4.356135606765747s
Availability | SPARQL endpoint availability check for French School Program took 4.100799560546875e-05s
Availability | VoID file availability check for French School Program took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for French School Program took 0.263688325881958s
Reputation | Calculation of the PageRank for French School Program took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for French School Program took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for French School Program took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for French School Program took 2.9325485229492188e-05s
Believability | Calculation of trust value for French School Program took 6.9141387939453125e-06s
INFO | --- Analysis for french-school-program took 2.7990095615386963s
Availability | SPARQL endpoint availability check for French School System took 4.172325134277344e-05s
Availability | VoID file availability check for French School System took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for French School System took 0.2604966163635254s
Reputation | Calculation of the PageRank for French School System took 0.020920753479003906s
Interlinking | Calculation of Degree of Connection for French School System took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for French School System took 3.409385681152344e-05s
Believability | Calculation of trust value for French School System took 7.62939453125e-06s
INFO | --- Analysis for french-school-system took 2.8542916774749756s
Availability | SPARQL endpoint availability check for French TimeBank took 4.4345855712890625e-05s
Availability | VoID file availability check for French TimeBank took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.25292348861694336s
Reputation | Calculation of the PageRank for French TimeBank took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.552436828613281e-05s
Believability | Calculation of trust value for French TimeBank took 7.3909759521484375e-06s
INFO | --- Analysis for french-timebank took 2.837484836578369s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.8215851783752441s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.2595090866088867s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 8.606910705566406e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 4.76837158203125e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.390217065811157s
Availability | SPARQL endpoint availability check for DailyMed took 0.7827024459838867s
Availability | VoID file availability check for DailyMed took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2733616828918457s
Reputation | Calculation of the PageRank for DailyMed took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.560585021972656e-05s
Believability | Calculation of trust value for DailyMed took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.871917486190796s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7165639400482178s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.273984432220459s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.02140522003173828s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0009005069732666016s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 9.72747802734375e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 7.867813110351562e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.323069095611572s
Availability | SPARQL endpoint availability check for Diseasome took 0.7219083309173584s
Availability | VoID file availability check for Diseasome took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Diseasome took 0.24285435676574707s
Reputation | Calculation of the PageRank for Diseasome took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010943412780761719s
Believability | Calculation of trust value for Diseasome took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.580053806304932s
Availability | SPARQL endpoint availability check for DrugBank took 0.7334599494934082s
Availability | VoID file availability check for DrugBank took 0.0012960433959960938s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2842991352081299s
Reputation | Calculation of the PageRank for DrugBank took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for DrugBank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DrugBank took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011348724365234375s
Believability | Calculation of trust value for DrugBank took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.649789571762085s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.7007331848144531s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.26717090606689453s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020951509475708008s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.170967102050781e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.391574144363403s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7347533702850342s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.24709463119506836s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.796287536621094e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.358865261077881s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.7574777603149414s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2642054557800293s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.581710815429688e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-eures took 4.366206884384155s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.7289166450500488s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2537872791290283s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.679794311523438e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 4.999772071838379s
Availability | SPARQL endpoint availability check for MediCare took 0.7324731349945068s
Availability | VoID file availability check for MediCare took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for MediCare took 0.2640726566314697s
Reputation | Calculation of the PageRank for MediCare took 0.021142005920410156s
Interlinking | Calculation of Degree of Connection for MediCare took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.1484832763671875e-05s
Believability | Calculation of trust value for MediCare took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-medicare took 5.076946020126343s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7463746070861816s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.27335667610168457s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.534027099609375e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 9.059906005859375e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.347538232803345s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7312254905700684s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.306201696395874s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020758867263793945s
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.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.560585021972656e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-sider took 5.162390470504761s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7657220363616943s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.24221587181091309s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.581710815429688e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.390466690063477s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 5.650520324707031e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.25339508056640625s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 2.9802322387695312e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 7.3909759521484375e-06s
INFO | --- Analysis for galen_from_co-odeorg took 2.805131435394287s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.482269287109375e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0008254051208496094s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.261707067489624s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.021214723587036133s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0008912086486816406s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.57763671875e-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 6.384856462478638s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.410743713378906e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.25873708724975586s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010561943054199219s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 7.867813110351562e-06s
INFO | --- Analysis for garnicaplywood took 3.700296401977539s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.363059997558594e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.2554738521575928s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020772933959960938s
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.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.441375732421875e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.1920928955078125e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 6.6014862060546875s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.2544434070587158s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0007717609405517578s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.26751136779785156s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00010824203491210938s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for gemet took 4.777701377868652s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.4345855712890625e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.2455143928527832s
Reputation | Calculation of the PageRank for gemet-annotated took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.600120544433594e-05s
Believability | Calculation of trust value for gemet-annotated took 8.821487426757812e-06s
INFO | --- Analysis for gemet-annotated took 2.8635621070861816s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7602205276489258s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2616429328918457s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.695487976074219e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 7.152557373046875e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.0913615226745605s
Availability | SPARQL endpoint availability check for geo.place took 4.291534423828125e-05s
Availability | VoID file availability check for geo.place took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for geo.place took 0.2569451332092285s
Reputation | Calculation of the PageRank for geo.place took 0.020985126495361328s
Interlinking | Calculation of Degree of Connection for geo.place took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.2901763916015625e-05s
Believability | Calculation of trust value for geo.place took 8.106231689453125e-06s
INFO | --- Analysis for geo_place took 2.828571081161499s
Availability | SPARQL endpoint availability check for geodomainwn took 4.458427429199219e-05s
Availability | VoID file availability check for geodomainwn took 0.0010216236114501953s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.25238704681396484s
Reputation | Calculation of the PageRank for geodomainwn took 0.02103137969970703s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.9114227294921875e-05s
Believability | Calculation of trust value for geodomainwn took 7.867813110351562e-06s
INFO | --- Analysis for geodomainwn took 6.665328025817871s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.5299530029296875e-05s
Availability | VoID file availability check for GeoEcuador took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.25193238258361816s
Reputation | Calculation of the PageRank for GeoEcuador took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.937980651855469e-05s
Believability | Calculation of trust value for GeoEcuador took 6.4373016357421875e-06s
INFO | --- Analysis for geoecuador took 12.51109766960144s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2323660850524902s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.24474287033081055s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.02091670036315918s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.985664367675781e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 8.106231689453125e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.19148516654968s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.2586038112640381s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.02106761932373047s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.2901763916015625e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.867813110351562e-06s
INFO | --- Analysis for geographic-openuplabs took 2.905815839767456s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.49015212059020996s
Availability | VoID file availability check for GeoLinkedData took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.24702739715576172s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 9.012222290039062e-05s
Believability | Calculation of trust value for GeoLinkedData took 4.76837158203125e-06s
INFO | --- Analysis for geolinkeddata took 3.8905510902404785s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.1923205852508545s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005819797515869141s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 12.513397216796875s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.3798975944519043s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.14122223854064941s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.4355709552764893s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.22455906867980957s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.1662125587463379s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.19334650039672852s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.10395932197570801s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.09006142616271973s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06974911689758301s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.08907675743103027s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.8629653453826904s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.10369062423706055s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.10919666290283203s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.13654136657714844s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.10279154777526855s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.06955170631408691s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.09571123123168945s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.489660739898682s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 8.58306884765625e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06211686134338379s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.0627133846282959s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.09623456001281738s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.07694578170776367s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06999826431274414s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.15451598167419434s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1514739990234375s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.6219639778137207s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 0.7959592342376709s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.09781241416931152s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.07583761215209961s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06866025924682617s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.3000361919403076s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.0075528621673583984s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.23169732093811035s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.07602620124816895s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.1954364776611328s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5408217906951904s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.301607131958008s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.5211644172668457s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.688638687133789s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17982006072998047s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.0754706859588623s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.1391301155090332s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.24734973907470703s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.726119995117188e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 0.4249446392059326s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 56.67485809326172s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.458427429199219e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.000579833984375s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2692594528198242s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00048422813415527344s
Believability | Calculation of trust value for GeoNames Semantic Web took 6.4373016357421875e-06s
INFO | --- Analysis for geonames-semantic-web took 3.0343868732452393s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5432717800140381s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.292677640914917s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.02027440071105957s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.0001361370086669922s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 7.3909759521484375e-06s
INFO | --- Analysis for geospecies took 5.7386155128479s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.363059997558594e-05s
Availability | VoID file availability check for GeoWordNet took 0.0007770061492919922s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2688281536102295s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.745887756347656e-05s
Believability | Calculation of trust value for GeoWordNet took 7.3909759521484375e-06s
INFO | --- Analysis for geowordnet took 6.974291086196899s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.07246112823486328s
Availability | VoID file availability check for German labor law thesaurus took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.25359392166137695s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.821487426757812e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.3419971466064453s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.458427429199219e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.26677584648132324s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0008676052093505859s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.696846008300781e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.3113021850585938e-05s
INFO | --- Analysis for germlex took 2.6685733795166016s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.4366662502288818s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.24897098541259766s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.608268737792969e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0251998901367188e-05s
INFO | --- Analysis for gesis-thesoz took 6.7844977378845215s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.69240140914917s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.3161814212799072s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.653236389160156e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for getty-aat took 16.31683349609375s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.2699549198150635s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.24691152572631836s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.316734313964844e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 6.67572021484375e-06s
INFO | --- Analysis for getty-tgn took 12.73138976097107s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.25431203842163086s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.2567472457885742s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.021073102951049805s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.0994415283203125e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 6.67572021484375e-06s
INFO | --- Analysis for gipuzkoademografia took 2.668860912322998s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 5.6743621826171875e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.25124645233154297s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 2.9802322387695312e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 6.9141387939453125e-06s
INFO | --- Analysis for glastonbury-2011 took 5.349016427993774s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.887580871582031e-05s
Availability | VoID file availability check for Global Change Information System took 0.00032210350036621094s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.2536320686340332s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020879030227661133s
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.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.0994415283203125e-05s
Believability | Calculation of trust value for Global Change Information System took 7.62939453125e-06s
INFO | --- Analysis for global-change-information-system took 2.8268051147460938s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 5.316734313964844e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.26192641258239746s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0010764598846435547s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.0067901611328125e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 7.3909759521484375e-06s
INFO | --- Analysis for global-hunger-index-2011 took 2.775923252105713s
Availability | SPARQL endpoint availability check for Glottolog took 4.3392181396484375e-05s
Availability | VoID file availability check for Glottolog took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Glottolog took 0.25748395919799805s
Reputation | Calculation of the PageRank for Glottolog took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Glottolog took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Glottolog took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.054473876953125e-05s
Believability | Calculation of trust value for Glottolog took 7.62939453125e-06s
INFO | --- Analysis for glottolog took 6.261281728744507s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.4345855712890625e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2552344799041748s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.02076244354248047s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010633468627929688s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 7.3909759521484375e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 9.542584896087646s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.2438507080078125e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.0003135204315185547s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.24028968811035156s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 3.0279159545898438e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 7.62939453125e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.770658493041992s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.172325134277344e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.246506929397583s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007383823394775391s
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.198883056640625e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.755979061126709s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.506111145019531e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2528808116912842s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.1021575927734375e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 8.106231689453125e-06s
INFO | --- Analysis for gold took 3.9906158447265625s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.315376281738281e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.2578549385070801s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.461143493652344e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 8.106231689453125e-06s
INFO | --- Analysis for googleart-wrapper took 2.589932918548584s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.12689828872680664s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.24331045150756836s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020661115646362305s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 4.291534423828125e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 7.152557373046875e-06s
INFO | --- Analysis for govagribus-denmark took 34.5552659034729s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.367173671722412s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.2549605369567871s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.368492126464844e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 23.789547443389893s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.56917405128479s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.24573707580566406s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020919084548950195s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 9.107589721679688e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.4836273193359375e-06s
INFO | --- Analysis for govtrack took 9.79217529296875s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.506111145019531e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.2654602527618408s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.9604644775390625e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.7404556274414062e-05s
INFO | --- Analysis for greek-administrative-geography took 2.4859251976013184s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.17534232139587402s
Availability | VoID file availability check for Greek Wordnet took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2729225158691406s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 6.079673767089844e-05s
Believability | Calculation of trust value for Greek Wordnet took 8.106231689453125e-06s
INFO | --- Analysis for greek-wordnet took 2.5245468616485596s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.4345855712890625e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.24945592880249023s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010180473327636719s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 7.915508508682251s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.1828432083129883s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.26822686195373535s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.57763671875e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 8.344650268554688e-06s
INFO | --- Analysis for grrp took 3.559095621109009s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.0934667587280273s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2576472759246826s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 7.963180541992188e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 4.76837158203125e-06s
INFO | --- Analysis for grrt took 3.4056639671325684s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.7206878662109375e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.2673475742340088s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.104873657226562e-05s
Believability | Calculation of trust value for Project Gutenberg took 8.344650268554688e-06s
INFO | --- Analysis for gutenberg took 8.311285972595215s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 5.459785461425781e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.24132347106933594s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.075599670410156e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 7.3909759521484375e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.82212495803833s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.363059997558594e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0003261566162109375s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.2500779628753662s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007512569427490234s
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 8.106231689453125e-06s
INFO | --- Analysis for heartfailure took 2.8571527004241943s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.814327716827393s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.26001453399658203s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.021076440811157227s
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.430511474609375e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.315376281738281e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 7.152557373046875e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 120.31674265861511s
Availability | SPARQL endpoint availability check for Hedatuz took 0.20359468460083008s
Availability | VoID file availability check for Hedatuz took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.268481969833374s
Reputation | Calculation of the PageRank for Hedatuz took 0.02031540870666504s
Interlinking | Calculation of Degree of Connection for Hedatuz took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.743171691894531e-05s
Believability | Calculation of trust value for Hedatuz took 7.152557373046875e-06s
INFO | --- Analysis for hedatuz took 2.8398420810699463s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.15029430389404297s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.000354766845703125s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2639353275299072s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00015425682067871094s
Believability | Calculation of trust value for Hellenic Fire Brigade took 9.298324584960938e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.4845376014709473s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.01210165023803711s
Availability | VoID file availability check for Hellenic Police took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.2636580467224121s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001277923583984375s
Believability | Calculation of trust value for Hellenic Police took 4.76837158203125e-06s
INFO | --- Analysis for hellenic-police took 2.371067762374878s
Availability | SPARQL endpoint availability check for Homologene took 4.1484832763671875e-05s
Availability | VoID file availability check for Homologene took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Homologene took 0.25536227226257324s
Reputation | Calculation of the PageRank for Homologene took 0.02080249786376953s
Interlinking | Calculation of Degree of Connection for Homologene took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Homologene took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.4809112548828125e-05s
Believability | Calculation of trust value for Homologene took 7.867813110351562e-06s
INFO | --- Analysis for homologene took 2.7572057247161865s
Availability | SPARQL endpoint availability check for Noticias Universia took 4.172325134277344e-05s
Availability | VoID file availability check for Noticias Universia took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.2492058277130127s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 2.86102294921875e-05s
Believability | Calculation of trust value for Noticias Universia took 6.9141387939453125e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 2.836290121078491s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.2438507080078125e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.2405402660369873s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.0279159545898438e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 6.9141387939453125e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.914393186569214s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.172325134277344e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.29746389389038086s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.314018249511719e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 6.9141387939453125e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.876436948776245s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 5.7697296142578125e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00032782554626464844s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2547626495361328s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.022139787673950195s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.552436828613281e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 8.58306884765625e-06s
INFO | --- Analysis for hud-library-usagedata took 2.830714702606201s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.2606515884399414s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.25493741035461426s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00011014938354492188s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.4066696166992188e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 3.8788528442382812s
Availability | SPARQL endpoint availability check for IATE RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for IATE RDF took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.25245118141174316s
Reputation | Calculation of the PageRank for IATE RDF took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for IATE RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.695487976074219e-05s
Believability | Calculation of trust value for IATE RDF took 7.867813110351562e-06s
INFO | --- Analysis for iate-rdf took 2.5503084659576416s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 5.945211887359619s
Availability | VoID file availability check for IATI as Linked Data took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.26782894134521484s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.021022319793701172s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.821487426757812e-05s
Believability | Calculation of trust value for IATI as Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for iati-as-linked-data took 12.964056730270386s
Availability | SPARQL endpoint availability check for ICANE took 0.34528470039367676s
Availability | VoID file availability check for ICANE took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for ICANE took 0.2712686061859131s
Reputation | Calculation of the PageRank for ICANE took 0.020929813385009766s
Interlinking | Calculation of Degree of Connection for ICANE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICANE took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.511543273925781e-05s
Believability | Calculation of trust value for ICANE took 5.0067901611328125e-06s
INFO | --- Analysis for icane took 3.4506382942199707s
Availability | SPARQL endpoint availability check for ichoose took 0.13638639450073242s
Availability | VoID file availability check for ichoose took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for ichoose took 0.26355934143066406s
Reputation | Calculation of the PageRank for ichoose took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for ichoose took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.890296936035156e-05s
Believability | Calculation of trust value for ichoose took 7.152557373046875e-06s
INFO | --- Analysis for ichoose took 41.35145092010498s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.267692565917969e-05s
Availability | VoID file availability check for Identifiers.org took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.24794793128967285s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020846843719482422s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 4.00543212890625e-05s
Believability | Calculation of trust value for Identifiers.org took 8.58306884765625e-06s
INFO | --- Analysis for identifiers-org took 2.825503349304199s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 7.62939453125e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.00037789344787597656s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2567131519317627s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02108144760131836s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0009763240814208984s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 9.34600830078125e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 8.821487426757812e-06s
INFO | --- Analysis for idreffr took 3.3441998958587646s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.8650870323181152s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.24147295951843262s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.863739013671875e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 7.152557373046875e-06s
INFO | --- Analysis for ids took 3.6683523654937744s
Availability | SPARQL endpoint availability check for ietflang took 4.38690185546875e-05s
Availability | VoID file availability check for ietflang took 0.0007984638214111328s
Completeness | Calculation of interlinking completeness for ietflang took 0.2414536476135254s
Reputation | Calculation of the PageRank for ietflang took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for ietflang took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.792213439941406e-05s
Believability | Calculation of trust value for ietflang took 8.344650268554688e-06s
INFO | --- Analysis for ietflang took 12.387669324874878s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.15655303001403809s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.25191545486450195s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 2.9802322387695312e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 8.344650268554688e-06s
INFO | --- Analysis for iislod-test took 2.595491886138916s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.042038917541504s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006275177001953125s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 40.89678192138672s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.3106682300567627s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.52426815032959s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.1461567878723145s
Versatility | Languages check for Imagesnippets Image Descriptions took 19.052600145339966s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 7.976544618606567s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6445930004119873s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.6863150596618652s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.66495680809021s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.6855728626251221s
License | MR license check for Imagesnippets Image Descriptions took 0.6765048503875732s
License | HR license check for Imagesnippets Image Descriptions took 30.674493551254272s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7043561935424805s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.446277141571045s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.3650829792022705s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.6863431930541992s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.6727550029754639s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6910371780395508s
Performance | Throughput check for Imagesnippets Image Descriptions took 12.965426683425903s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 8.082389831542969e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.6608226299285889s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.6823501586914062s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6902821063995361s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6613991260528564s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7064354419708252s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.3718273639678955s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.3625173568725586s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 49.74150848388672s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.6839179992675781s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6768128871917725s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.6684515476226807s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.6926321983337402s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.762714385986328s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 15.26568055152893s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.545728921890259s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00016164779663085938s
Security | Sign check for Imagesnippets Image Descriptions took 0.7014729976654053s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.740825891494751s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020738601684570312s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 0.000102996826171875s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.9073486328125e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 7.867813110351562e-06s
INFO | --- Analysis for imagesnippets took 409.5183343887329s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.4568464756011963s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.6730663776397705s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.797645568847656e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for imf-linked-data took 3.643313407897949s
Availability | SPARQL endpoint availability check for IMGpedia took 9.489059448242188e-05s
Availability | VoID file availability check for IMGpedia took 0.0002257823944091797s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2533552646636963s
Reputation | Calculation of the PageRank for IMGpedia took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.1948089599609375e-05s
Believability | Calculation of trust value for IMGpedia took 7.62939453125e-06s
INFO | --- Analysis for imgpedia took 2.844313859939575s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.458427429199219e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.2617528438568115s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.0209805965423584s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 3.361701965332031e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 8.344650268554688e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 2.835151433944702s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.482269287109375e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.24950623512268066s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.4332275390625e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 7.62939453125e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.8056201934814453s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.410743713378906e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.26290273666381836s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020897865295410156s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.123283386230469e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 9.775161743164062e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.8132665157318115s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 5.53131103515625e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.24653220176696777s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.021118640899658203s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.2901763916015625e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 7.62939453125e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.7912721633911133s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.410743713378906e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2669179439544678s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00011134147644042969s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 7.867813110351562e-06s
INFO | --- Analysis for ineverycrea took 18.395039796829224s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.4345855712890625e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2619969844818115s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.584426879882812e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.344650268554688e-06s
INFO | --- Analysis for ineverycrea-argentina took 9.5248122215271s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 271.147340297699s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.2893397808074951s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02103734016418457s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.62939453125e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.152557373046875e-06s
INFO | --- Analysis for influence-tracker-dataset took 566.760383605957s
Availability | SPARQL endpoint availability check for INSEMTIVES took 5.1021575927734375e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.7582871913909912s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.02099466323852539s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.0517578125e-05s
Believability | Calculation of trust value for INSEMTIVES took 8.106231689453125e-06s
INFO | --- Analysis for insemtives took 3.873433828353882s
Availability | SPARQL endpoint availability check for instagram.person took 4.315376281738281e-05s
Availability | VoID file availability check for instagram.person took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for instagram.person took 0.27078747749328613s
Reputation | Calculation of the PageRank for instagram.person took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for instagram.person took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for instagram.person took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.62396240234375e-05s
Believability | Calculation of trust value for instagram.person took 7.867813110351562e-06s
INFO | --- Analysis for instagram_person took 2.924353837966919s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.267692565917969e-05s
Availability | VoID file availability check for instagram.videoobject took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.6864871978759766s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 2.8848648071289062e-05s
Believability | Calculation of trust value for instagram.videoobject took 8.344650268554688e-06s
INFO | --- Analysis for instagram_videoobject took 3.726757287979126s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.1961669921875e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.24355125427246094s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020823955535888672s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.743171691894531e-05s
Believability | Calculation of trust value for Instance Hub Countries took 8.821487426757812e-06s
INFO | --- Analysis for instance-hub-countries took 2.8052515983581543s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.553794860839844e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.24370384216308594s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.0210115909576416s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.24249267578125e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.2471811771392822s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.2534964084625244s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-organizations took 2.8135616779327393s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.220008850097656e-05s
Availability | VoID file availability check for Instance Hub People took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.2585906982421875s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 2.9802322387695312e-05s
Believability | Calculation of trust value for Instance Hub People took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-people took 2.792965888977051s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 5.4836273193359375e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.26717329025268555s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.021578311920166016s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.409385681152344e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.842174530029297s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.38690185546875e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.26877284049987793s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0008013248443603516s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 8.344650268554688e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.8769500255584717s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.363059997558594e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.26808786392211914s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020789384841918945s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0010204315185546875s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.743171691894531e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.794016122817993s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.4345855712890625e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.24824810028076172s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020702123641967773s
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.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 8.821487426757812e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.8715157508850098s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.2438507080078125e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2612950801849365s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 8.344650268554688e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.8067538738250732s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 6.866455078125e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.24429869651794434s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.8123223781585693s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.410743713378906e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.26275086402893066s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.075599670410156e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.7958872318267822s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.363059997558594e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0003223419189453125s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.24270129203796387s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 2.956390380859375e-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.8164894580841064s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.315376281738281e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.25589823722839355s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010609626770019531s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for interactivemaps-gnoss took 21.446786403656006s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.9114227294921875e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2662179470062256s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.0994415283203125e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 7.867813110351562e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.8940505981445312s
Availability | SPARQL endpoint availability check for intervalue took 0.1249992847442627s
Availability | VoID file availability check for intervalue took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for intervalue took 0.2635538578033447s
Reputation | Calculation of the PageRank for intervalue took 0.021649837493896484s
Interlinking | Calculation of Degree of Connection for intervalue took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0008864402770996094s
Interlinking | Calculation of Clustering coefficient for intervalue took 7.82012939453125e-05s
Believability | Calculation of trust value for intervalue took 8.58306884765625e-06s
INFO | --- Analysis for intervalue took 2.460036516189575s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.38690185546875e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.24970746040344238s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02080678939819336s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.76837158203125e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 7.3909759521484375e-06s
INFO | --- Analysis for iptc-newscodes took 2.992520570755005s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.4345855712890625e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.00032520294189453125s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.2613353729248047s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0207517147064209s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0008077621459960938s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.123283386230469e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 8.106231689453125e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.815323829650879s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.397106409072876s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.000804901123046875s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.2611963748931885s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020667314529418945s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.965896606445312e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 7.867813110351562e-06s
INFO | --- Analysis for iserve took 9.068075180053711s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.156086683273315s
Availability | VoID file availability check for ISIC V4 took 0.0009410381317138672s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.26194071769714355s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.981590270996094e-05s
Believability | Calculation of trust value for ISIC V4 took 6.67572021484375e-06s
INFO | --- Analysis for isic-v4 took 114.88853049278259s
Availability | SPARQL endpoint availability check for Isidore took 4.291534423828125e-05s
Availability | VoID file availability check for Isidore took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Isidore took 0.24278783798217773s
Reputation | Calculation of the PageRank for Isidore took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for Isidore took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Isidore took 3.1948089599609375e-05s
Believability | Calculation of trust value for Isidore took 1.1920928955078125e-05s
INFO | --- Analysis for isidore took 2.8049304485321045s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 5.435943603515625e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.24977850914001465s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.075599670410156e-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.8658981323242188s
Availability | SPARQL endpoint availability check for ISOcat took 5.4836273193359375e-05s
Availability | VoID file availability check for ISOcat took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for ISOcat took 0.24140453338623047s
Reputation | Calculation of the PageRank for ISOcat took 0.020958423614501953s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.794929504394531e-05s
Believability | Calculation of trust value for ISOcat took 1.2159347534179688e-05s
INFO | --- Analysis for isocat took 32.90253949165344s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.410743713378906e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.26450276374816895s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.6716461181640625e-05s
Believability | Calculation of trust value for ISOcat-metadata took 9.775161743164062e-06s
INFO | --- Analysis for isocat-metadata took 4.873753070831299s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 5.53131103515625e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.2745053768157959s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.0994415283203125e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 9.059906005859375e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.879399538040161s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.29471802711486816s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0005295276641845703s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.352164506912231s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.6980550289154053s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22133469581604004s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.121959686279297s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 92.04829525947571s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19874835014343262s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11087369918823242s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2511935234069824s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20258235931396484s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14696335792541504s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24031496047973633s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.4230694770813s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16762256622314453s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2231159210205078s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3709855079650879s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17066740989685059s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.23245787620544434s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19001412391662598s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.698821306228638s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010991096496582031s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17285752296447754s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3051590919494629s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5189099311828613s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.43285369873046875s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22344756126403809s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3143947124481201s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2146434783935547s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 15.237967252731323s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14783525466918945s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17087244987487793s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14114642143249512s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.114798545837402s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31682443618774414s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.26836657524108887s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18516826629638672s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.728095531463623s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9746739864349365s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.499802112579346s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.326673984527588s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.898892164230347s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2881929874420166s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18112945556640625s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15760469436645508s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.82769250869751s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7889411449432373s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.021235227584838867s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010561943054199219s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.1457672119140625e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.58306884765625e-06s
INFO | --- Analysis for ispra-lod-place took 461.51719427108765s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.863739013671875e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2530648708343506s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0008609294891357422s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.266334533691406e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-rmn took 3.707730531692505s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.14606404304504395s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0006268024444580078s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 9.158813238143921s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.7184069156646729s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.20150089263916016s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 3.0911037921905518s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.80536389350891s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.1741650104522705s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.1164696216583252s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.17893028259277344s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.17215704917907715s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.1356511116027832s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.21372270584106445s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.29607486724854s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.1689891815185547s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.0851643085479736s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.3898041248321533s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.18090248107910156s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.17556190490722656s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.14839935302734375s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.558377265930176s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.033348083496094e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.1677403450012207s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.24130511283874512s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.42714881896972656s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4215817451477051s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.17772483825683594s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.285266637802124s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.1503593921661377s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 15.29810094833374s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.13298726081848145s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.15528488159179688s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.14985942840576172s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 3.91121768951416s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.31601381301879883s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.26964616775512695s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.14538145065307617s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.721164464950562s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9705245494842529s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 4.082294225692749s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.3330104351043701s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.893540620803833s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.29131054878234863s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.18549537658691406s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.1581568717956543s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 12.608031272888184s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.37492942810058594s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 6.103515625e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.790855407714844e-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 6.4373016357421875e-06s
INFO | --- Analysis for ispra-lod-ron took 463.600834608078s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.3392181396484375e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.2659144401550293s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.147125244140625e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 6.9141387939453125e-06s
INFO | --- Analysis for ispra-lod-sc took 3.2778258323669434s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.674743890762329s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.2572519779205322s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020406007766723633s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.630752563476562e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 4.76837158203125e-06s
INFO | --- Analysis for istat-immigration took 4.403604507446289s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 5.1975250244140625e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.2382802963256836s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020758628845214844s
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.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.266334533691406e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 8.344650268554688e-06s
INFO | --- Analysis for istat-immigrazione took 3.1783547401428223s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.18104338645935059s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.24263882637023926s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020936965942382812s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0009455680847167969s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 4.00543212890625e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 6.67572021484375e-06s
INFO | --- Analysis for it-aifa-drug-prices took 2.769136905670166s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.0186314582824707s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.26202940940856934s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.02164602279663086s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 8.082389831542969e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 7.62939453125e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 3.3446812629699707s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.315376281738281e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.2760500907897949s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020644426345825195s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.0994415283203125e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 8.106231689453125e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.862250328063965s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.982948303222656e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.24193024635314941s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.0994415283203125e-05s
Believability | Calculation of trust value for IWMI Research Reports took 9.775161743164062e-06s
INFO | --- Analysis for iwmi-research-reports took 2.7558999061584473s
Availability | SPARQL endpoint availability check for IWN took 9.1552734375e-05s
Availability | VoID file availability check for IWN took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for IWN took 0.2604529857635498s
Reputation | Calculation of the PageRank for IWN took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for IWN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for IWN took 3.719329833984375e-05s
Believability | Calculation of trust value for IWN took 7.62939453125e-06s
INFO | --- Analysis for iwn took 5.786003351211548s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.291534423828125e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.27570486068725586s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.021753549575805664s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.814697265625e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 7.152557373046875e-06s
INFO | --- Analysis for j-global-knowledge took 2.829916477203369s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.315376281738281e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.2490370273590088s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 6.651878356933594e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 9.5367431640625e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.823190927505493s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 7.956667900085449s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0007379055023193359s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.26680779457092285s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.341934204101562e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 9.5367431640625e-06s
INFO | --- Analysis for jamendo-dbtune took 23.49539041519165s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.410743713378906e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2587864398956299s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.696846008300781e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for japan-radioactivity-stat took 3.698596477508545s
Availability | SPARQL endpoint availability check for JEL Classification took 4.410743713378906e-05s
Availability | VoID file availability check for JEL Classification took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.25746965408325195s
Reputation | Calculation of the PageRank for JEL Classification took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0008752346038818359s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.4809112548828125e-05s
Believability | Calculation of trust value for JEL Classification took 7.62939453125e-06s
INFO | --- Analysis for jel-classification took 4.47566032409668s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.0897793769836426s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2669253349304199s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.361701965332031e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 7.867813110351562e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 6.683687686920166s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 260.62156867980957s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.26850199699401855s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.021037578582763672s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.702278137207031e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 8.58306884765625e-06s
INFO | --- Analysis for jita took 539.4746279716492s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 5.316734313964844e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.6876890659332275s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020804405212402344s
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.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.4809112548828125e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 8.106231689453125e-06s
INFO | --- Analysis for jmdict took 4.734455823898315s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.051995754241943s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.29270315170288086s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0008134841918945312s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 0.00011587142944335938s
Believability | Calculation of trust value for John Goodwin's Family Tree took 9.298324584960938e-06s
INFO | --- Analysis for john-goodwins-family-tree took 41.142152547836304s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.9298727512359619s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.25518798828125s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.937980651855469e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 9.298324584960938e-06s
INFO | --- Analysis for jrc-names-mlode took 4.153359413146973s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.458427429199219e-05s
Availability | VoID file availability check for JudaicaLink took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2628448009490967s
Reputation | Calculation of the PageRank for JudaicaLink took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.000118255615234375s
Believability | Calculation of trust value for JudaicaLink took 8.344650268554688e-06s
INFO | --- Analysis for judaicalink took 22.411027431488037s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.2538323402404785s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.02097773551940918s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.123283386230469e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 1.1205673217773438e-05s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.758960485458374s
Availability | SPARQL endpoint availability check for KAKEN took 4.315376281738281e-05s
Availability | VoID file availability check for KAKEN took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for KAKEN took 0.2549598217010498s
Reputation | Calculation of the PageRank for KAKEN took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.170967102050781e-05s
Believability | Calculation of trust value for KAKEN took 8.106231689453125e-06s
INFO | --- Analysis for kaken took 3.2266435623168945s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06300616264343262s
Availability | VoID file availability check for Kallikratis municipalities took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.26398396492004395s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.441375732421875e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 6.67572021484375e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.823155641555786s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.410743713378906e-05s
Availability | VoID file availability check for Openflights Routes took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.24067306518554688s
Reputation | Calculation of the PageRank for Openflights Routes took 0.02097916603088379s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.075599670410156e-05s
Believability | Calculation of trust value for Openflights Routes took 2.2649765014648438e-05s
INFO | --- Analysis for kasabi-openflights-routes took 2.7554454803466797s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.363059997558594e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.26433634757995605s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 7.2479248046875e-05s
Believability | Calculation of trust value for Klappstuhlclub took 5.245208740234375e-06s
INFO | --- Analysis for klappstuhlclub took 12.45604133605957s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.810001373291016s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0003218650817871094s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2753760814666748s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020994186401367188s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 7.128715515136719e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 8.106231689453125e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.21932339668274s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.220008850097656e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.24512362480163574s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.021547317504882812s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0009007453918457031s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 5.745887756347656e-05s
Believability | Calculation of trust value for Knowledge Forest took 8.344650268554688e-06s
INFO | --- Analysis for knowledge-map took 2.790389060974121s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.458427429199219e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.6925585269927979s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 7.390975952148438e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 8.344650268554688e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.806846380233765s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.649162292480469e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.23981618881225586s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.02092576026916504s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.170967102050781e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 8.344650268554688e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.7671022415161133s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.124641418457031e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.257549524307251s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.337860107421875e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 7.152557373046875e-06s
INFO | --- Analysis for ktr took 2.842817783355713s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.08828067779541016s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0007710456848144531s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2779834270477295s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.021103620529174805s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0010859966278076172s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 4.553794860839844e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 8.821487426757812e-06s
INFO | --- Analysis for kupkb took 10.511362075805664s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 7.224082946777344e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.26626086235046387s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.218650817871094e-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.816471576690674s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.197010278701782s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.28040337562561035s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 8.106231689453125e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 7.62939453125e-06s
INFO | --- Analysis for l3s-dblp took 47.625760316848755s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.100988388061523s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.23470473289489746s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.771087646484375e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 7.62939453125e-06s
INFO | --- Analysis for lak-dataset took 66.36264109611511s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.315376281738281e-05s
Availability | VoID file availability check for LATC Linksets took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.2650165557861328s
Reputation | Calculation of the PageRank for LATC Linksets took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 2.8371810913085938e-05s
Believability | Calculation of trust value for LATC Linksets took 7.867813110351562e-06s
INFO | --- Analysis for latc-linksets took 2.753852128982544s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.220008850097656e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.25197291374206543s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.021046161651611328s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.2901763916015625e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 7.152557373046875e-06s
INFO | --- Analysis for lcc took 3.2541449069976807s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 8.106231689453125e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.25776171684265137s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.021174907684326172s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0009853839874267578s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00014662742614746094s
Believability | Calculation of trust value for Library of Congress Subject Headings took 8.106231689453125e-06s
INFO | --- Analysis for lcsh took 5.085937023162842s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.4345855712890625e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0007979869842529297s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.25795650482177734s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.559226989746094e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 8.58306884765625e-06s
INFO | --- Analysis for lcsubjects took 2.8576552867889404s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.1484832763671875e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.2445235252380371s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 2.9802322387695312e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 6.9141387939453125e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.820258617401123s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 8.106231689453125e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.24782299995422363s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.075599670410156e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 6.198883056640625e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.8010265827178955s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.172325134277344e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.25283217430114746s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.8848648071289062e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 9.775161743164062e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.796567916870117s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.3392181396484375e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.259540319442749s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 2.9325485229492188e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 8.344650268554688e-06s
INFO | --- Analysis for legislation-openuplabs took 2.814455270767212s
Availability | SPARQL endpoint availability check for lemonUby took 4.4345855712890625e-05s
Availability | VoID file availability check for lemonUby took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for lemonUby took 0.25916624069213867s
Reputation | Calculation of the PageRank for lemonUby took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for lemonUby took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lemonUby took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.413459777832031e-05s
Believability | Calculation of trust value for lemonUby took 7.3909759521484375e-06s
INFO | --- Analysis for lemonuby took 3.1242618560791016s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.38690185546875e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.25328922271728516s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.3855438232421875e-05s
Believability | Calculation of trust value for LemonWiktionary took 9.059906005859375e-06s
INFO | --- Analysis for lemonwiktionary took 4.160221576690674s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.1840484142303467s
Availability | VoID file availability check for LEXIN-RDF took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2633657455444336s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 2.8848648071289062e-05s
Believability | Calculation of trust value for LEXIN-RDF took 8.344650268554688e-06s
INFO | --- Analysis for lexin-rdf took 5.6178138256073s
Availability | SPARQL endpoint availability check for lexinfo took 5.650520324707031e-05s
Availability | VoID file availability check for lexinfo took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for lexinfo took 0.24145269393920898s
Reputation | Calculation of the PageRank for lexinfo took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.988380432128906e-05s
Believability | Calculation of trust value for lexinfo took 7.867813110351562e-06s
INFO | --- Analysis for lexinfo took 2.712893009185791s
Availability | SPARQL endpoint availability check for Lexvo took 4.315376281738281e-05s
Availability | VoID file availability check for Lexvo took 0.0007708072662353516s
Completeness | Calculation of interlinking completeness for Lexvo took 0.3079230785369873s
Reputation | Calculation of the PageRank for Lexvo took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00020003318786621094s
Believability | Calculation of trust value for Lexvo took 8.58306884765625e-06s
INFO | --- Analysis for lexvo took 42.79529428482056s
Availability | SPARQL endpoint availability check for LIBRIS took 0.29301953315734863s
Availability | VoID file availability check for LIBRIS took 0.0006723403930664062s
Extra | Recovery of all triples for LIBRIS took 9.988712310791016s
Performance | Total latancy measurement for LIBRIS took 0.7427492141723633s
Amount of data | Number of triples check for LIBRIS took 24.851524353027344s
Interoperability | New terms check for LIBRIS took 15.24039077758789s
Versatility | Languages check for LIBRIS took 0.19211769104003906s
Interpretability | Number of blank nodes check for LIBRIS took 300.07835936546326s
Security | Check HTTPS for LIBRIS took 0.38352537155151367s
Interpretability | RDF structures check for LIBRIS took 0.5870361328125s
Versatility | Serialization formats check for LIBRIS took 0.2327413558959961s
Availability | RDF dump link check for LIBRIS took 0.14685630798339844s
License | MR license check for LIBRIS took 0.28475117683410645s
License | HR license check for LIBRIS took 0.230637788772583s
Amount of data | Number of property check for LIBRIS took 0.18799924850463867s
Understandability | Number of label check for LIBRIS took 0.6368827819824219s
Understandability | URI regex check for LIBRIS took 0.40009045600891113s
Understandability | Vocabs check for LIBRIS took 0.14809727668762207s
Verifiability | Authors check for LIBRIS took 0.18736815452575684s
Verifiability | Publishers check for LIBRIS took 0.16974234580993652s
Performance | Throughput check for LIBRIS took 11.174851655960083s
Amount of data | Check the number of entities for LIBRIS took 7.724761962890625e-05s
Verifiability | Contribs. check for LIBRIS took 0.1628401279449463s
Interlinking | sameAs chians check for LIBRIS took 0.2353827953338623s
Interlinking | skos check for LIBRIS took 0.37435007095336914s
Interlinking | skos check for LIBRIS took 0.13891220092773438s
Timeliness | dataset update frequency check for LIBRIS took 0.15756559371948242s
Currency | Creation date check for LIBRIS took 0.36435508728027344s
Currency | Modification date check for LIBRIS took 0.6434292793273926s
Rep.Conc. | URIs length for LIBRIS took 81.61248111724854s
Interoperability | New vocabularies check for LIBRIS took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.17815637588500977s
Accuracy | Check Functional Property for LIBRIS took 0.2000565528869629s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.13985991477966309s
Accuracy | Check Datatype consistency for LIBRIS took 0.27098894119262695s
Consistency | Disjoint class check for LIBRIS took 0.23094701766967773s
Consistency | Check Misplaced properties for LIBRIS took 61.13912391662598s
Consistency | Misplaced classes for LIBRIS took 1.1681559085845947s
Consistency | Check Ontology hijacking for LIBRIS took 3.6932942867279053s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3310673236846924s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 62.20518898963928s
Conciseness | Check Extensional conciseness for LIBRIS took 0.28630638122558594s
Conciseness | Check Intensional conciseness for LIBRIS took 0.38333821296691895s
Security | Sign check for LIBRIS took 0.36696434020996094s
Availability | Check URIs Dereferenciability for LIBRIS took 10.147951126098633s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.7132141590118408s
Reputation | Calculation of the PageRank for LIBRIS took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00010085105895996094s
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 1077.389146566391s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06230568885803223s
Availability | VoID file availability check for Public Library of Veroia took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.266054630279541s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02048182487487793s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.367134094238281e-05s
Believability | Calculation of trust value for Public Library of Veroia took 8.344650268554688e-06s
INFO | --- Analysis for libver took 4.312790632247925s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.10263442993164062s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.25159311294555664s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.344650268554688e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.245208740234375e-06s
INFO | --- Analysis for lichfield-spending took 3.3371973037719727s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 6.222724914550781e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.6975030899047852s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.147125244140625e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 8.821487426757812e-06s
INFO | --- Analysis for lime took 6.671510457992554s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.3392181396484375e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.2696247100830078s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0001087188720703125s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 8.344650268554688e-06s
INFO | --- Analysis for lingvoj took 5.156057357788086s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.24473190307617188s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.939338684082031e-05s
Believability | Calculation of trust value for Linked Crunchbase took 6.9141387939453125e-06s
INFO | --- Analysis for linked-crunchbase took 2.7223403453826904s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.188510894775391s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.25615692138671875s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020410537719726562s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.43865966796875e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.821487426757812e-06s
INFO | --- Analysis for linked-drugs took 19.208909511566162s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.6253204345703125e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.24193644523620605s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.584426879882812e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 5.7220458984375e-06s
INFO | --- Analysis for linked-edgar took 3.86590576171875s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 5.793571472167969e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.2583658695220947s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.822845458984375e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-eurostat took 3.9605515003204346s
Availability | SPARQL endpoint availability check for linked hypernyms took 7.82012939453125e-05s
Availability | VoID file availability check for linked hypernyms took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2559845447540283s
Reputation | Calculation of the PageRank for linked hypernyms took 0.021844148635864258s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.772445678710938e-05s
Believability | Calculation of trust value for linked hypernyms took 9.298324584960938e-06s
INFO | --- Analysis for linked-hypernyms took 3.197068214416504s
Availability | SPARQL endpoint availability check for Linked Life Data took 223.80325174331665s
Availability | VoID file availability check for Linked Life Data took 0.0008404254913330078s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.3141653537750244s
Reputation | Calculation of the PageRank for Linked Life Data took 0.02109670639038086s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0010075569152832031s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.7206878662109375e-05s
Believability | Calculation of trust value for Linked Life Data took 8.106231689453125e-06s
INFO | --- Analysis for linked-life-data took 684.4221098423004s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.3060605525970459s
Availability | VoID file availability check for Linked Logainm took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.24634575843811035s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.43865966796875e-05s
Believability | Calculation of trust value for Linked Logainm took 7.3909759521484375e-06s
INFO | --- Analysis for linked-logainm took 4.444392204284668s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked NUTS took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.26417088508605957s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020816802978515625s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.507469177246094e-05s
Believability | Calculation of trust value for Linked NUTS took 6.198883056640625e-06s
INFO | --- Analysis for linked-nuts took 3.7228305339813232s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 5.435943603515625e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.254730224609375s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 3.0279159545898438e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 3.250211715698242s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.588014841079712s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0003631114959716797s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.2614588737487793s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007684230804443359s
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 6.67572021484375e-06s
INFO | --- Analysis for linked-open-camera took 3.92814564704895s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.478041410446167s
Availability | VoID file availability check for Linked Open Commerce took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2500264644622803s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020476102828979492s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0517578125e-05s
Believability | Calculation of trust value for Linked Open Commerce took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-commerce took 12.897516250610352s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.2173285484313965s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.2647664546966553s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010442733764648438s
Believability | Calculation of trust value for Linked Open Data of Ecology took 9.775161743164062e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 3.5400896072387695s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2457425594329834s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020914554595947266s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.489059448242188e-05s
Believability | Calculation of trust value for Linked Open Numbers took 8.106231689453125e-06s
INFO | --- Analysis for linked-open-numbers took 2.4775946140289307s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.458427429199219e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.25664687156677246s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.790855407714844e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-piracy took 6.815425872802734s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 6.008148193359375e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.26441192626953125s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.02085089683532715s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0008692741394042969s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-senate took 2.838853597640991s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 1.471081018447876s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.2575063705444336s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.744529724121094e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 8.759651184082031s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.3392181396484375e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.24761724472045898s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.021145343780517578s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0008935928344726562s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.981590270996094e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.0067901611328125e-06s
INFO | --- Analysis for linked-periodicals took 2.4296329021453857s
Availability | SPARQL endpoint availability check for Linked Index took 7.534027099609375e-05s
Availability | VoID file availability check for Linked Index took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2527329921722412s
Reputation | Calculation of the PageRank for Linked Index took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Linked Index took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Index took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.511543273925781e-05s
Believability | Calculation of trust value for Linked Index took 7.62939453125e-06s
INFO | --- Analysis for linked-stockindex took 2.3145437240600586s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.652677774429321s
Availability | VoID file availability check for Linked Structured Product Labels took 0.001051187515258789s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.23913097381591797s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.695487976074219e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 8.58306884765625e-06s
INFO | --- Analysis for linked-structured-product-labels took 11.766315937042236s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.9436159133911133s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.24654006958007812s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.504753112792969e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 7.152557373046875e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 4.170241832733154s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.248677492141724s
Availability | VoID file availability check for Linked TCGA took 0.0008404254913330078s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.26031064987182617s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 0.00010228157043457031s
Believability | Calculation of trust value for Linked TCGA took 1.3828277587890625e-05s
INFO | --- Analysis for linked-tcga took 62.66929817199707s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.20279264450073242s
Availability | VoID file availability check for Linked User Feedback took 0.00021147727966308594s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.2655487060546875s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0008337497711181641s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 4.172325134277344e-05s
Believability | Calculation of trust value for Linked User Feedback took 9.298324584960938e-06s
INFO | --- Analysis for linked-user-feedback took 2.5649800300598145s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.5299530029296875e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0009751319885253906s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2516920566558838s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.02081012725830078s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0008635520935058594s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.940696716308594e-05s
Believability | Calculation of trust value for USPTO Patent data took 6.67572021484375e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.26987099647522s
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.00028252601623535156s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.25568628311157227s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 3.24249267578125e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 7.62939453125e-06s
INFO | --- Analysis for linked-web-apis took 2.822999954223633s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.220008850097656e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.24603033065795898s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.021323680877685547s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0009486675262451172s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.4332275390625e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 1.0251998901367188e-05s
INFO | --- Analysis for linkedarc took 3.176820755004883s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.08638501167297363s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.00037360191345214844s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2498307228088379s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.528594970703125e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 7.867813110351562e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.4912304878234863s
Availability | SPARQL endpoint availability check for LinkedCT took 1.4814507961273193s
Availability | VoID file availability check for LinkedCT took 0.0003368854522705078s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.26271700859069824s
Reputation | Calculation of the PageRank for LinkedCT took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00010514259338378906s
Believability | Calculation of trust value for LinkedCT took 7.867813110351562e-06s
INFO | --- Analysis for linkedct took 5.1480913162231445s
Availability | SPARQL endpoint availability check for LinkedGeoData took 391.8857591152191s
Availability | VoID file availability check for LinkedGeoData took 0.0008065700531005859s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.797189474105835s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.02148580551147461s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00013828277587890625s
Believability | Calculation of trust value for LinkedGeoData took 8.821487426757812e-06s
INFO | --- Analysis for linkedgeodata took 928.9444048404694s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 7.104873657226562e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.730046272277832s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.552436828613281e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 7.867813110351562e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 4.324282646179199s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.0425209999084473s
Availability | VoID file availability check for LinkedLCCN took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.26741456985473633s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010514259338378906s
Believability | Calculation of trust value for LinkedLCCN took 1.9311904907226562e-05s
INFO | --- Analysis for linkedlccn took 11.21161437034607s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.57763671875e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.265117883682251s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.02108454704284668s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.814697265625e-05s
Believability | Calculation of trust value for LinkedMarkMail took 9.059906005859375e-06s
INFO | --- Analysis for linkedmarkmail took 3.493812322616577s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 0.9193496704101562s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2649507522583008s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.0001385211944580078s
Believability | Calculation of trust value for Linked Movie DataBase took 8.821487426757812e-06s
INFO | --- Analysis for linkedmdb took 14.209096670150757s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.4409761428833008s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.26122379302978516s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.2479248046875e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for linkedspending took 4.293041944503784s
Availability | SPARQL endpoint availability check for LinkedStats took 4.220008850097656e-05s
Availability | VoID file availability check for LinkedStats took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2551157474517822s
Reputation | Calculation of the PageRank for LinkedStats took 0.021146059036254883s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 3.1948089599609375e-05s
Believability | Calculation of trust value for LinkedStats took 6.67572021484375e-06s
INFO | --- Analysis for linkedstats took 2.765094518661499s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.1484832763671875e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.26175427436828613s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020972728729248047s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.1948089599609375e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 9.5367431640625e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.8169407844543457s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.291534423828125e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.257920503616333s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.021813154220581055s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 4.601478576660156e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 7.867813110351562e-06s
INFO | --- Analysis for linking-open-drug-data took 2.795590400695801s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.04872918128967285s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.2481377124786377s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.022445201873779297s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0009107589721679688s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00011920928955078125s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 9.298324584960938e-06s
INFO | --- Analysis for linklion took 2.3665618896484375s
Availability | SPARQL endpoint availability check for Lion's Den took 4.1484832763671875e-05s
Availability | VoID file availability check for Lion's Den took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.24724435806274414s
Reputation | Calculation of the PageRank for Lion's Den took 0.021092891693115234s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.3855438232421875e-05s
Believability | Calculation of trust value for Lion's Den took 7.3909759521484375e-06s
INFO | --- Analysis for lionsden took 2.866067409515381s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 35.537344217300415s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.25872254371643066s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.021015405654907227s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0008146762847900391s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.5789947509765625e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 40.81181788444519s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.3392181396484375e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0003159046173095703s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.2721264362335205s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.02109503746032715s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.337860107421875e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 8.821487426757812e-06s
INFO | --- Analysis for livtdm took 2.806910991668701s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.363059997558594e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.23537111282348633s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 3.24249267578125e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 6.67572021484375e-06s
INFO | --- Analysis for livtdm2017 took 2.750422239303589s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.25969886779785156s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.266334533691406e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 7.3909759521484375e-06s
INFO | --- Analysis for lobi took 2.8413467407226562s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.2211594581604004s
Availability | VoID file availability check for lobid-organisations took 0.0008215904235839844s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.2787001132965088s
Reputation | Calculation of the PageRank for lobid-organisations took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 0.00010013580322265625s
Believability | Calculation of trust value for lobid-organisations took 1.1682510375976562e-05s
INFO | --- Analysis for lobid-organisations took 5.885292053222656s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.8750886917114258s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.26191043853759766s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010180473327636719s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 7.62939453125e-06s
INFO | --- Analysis for lobid-resources took 8.576820611953735s
Availability | SPARQL endpoint availability check for Linked Open Colors took 6.937980651855469e-05s
Availability | VoID file availability check for Linked Open Colors took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2594032287597656s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.224082946777344e-05s
Believability | Calculation of trust value for Linked Open Colors took 7.3909759521484375e-06s
INFO | --- Analysis for loc took 6.6269001960754395s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.57763671875e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.25456738471984863s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.123283386230469e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 6.9141387939453125e-06s
INFO | --- Analysis for locv took 31.54176616668701s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7276532649993896s
Availability | VoID file availability check for LOD-a-lot took 0.0008628368377685547s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.268923282623291s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.528594970703125e-05s
Believability | Calculation of trust value for LOD-a-lot took 7.3909759521484375e-06s
INFO | --- Analysis for lod-a-lot took 13.74389123916626s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.220008850097656e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.26511478424072266s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.020745277404785156s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 3.170967102050781e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 7.62939453125e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.758009195327759s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.4345855712890625e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.2572779655456543s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.24249267578125e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 6.9141387939453125e-06s
INFO | --- Analysis for lod-taiwan took 2.8129608631134033s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.38690185546875e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0012698173522949219s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.26392507553100586s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.893013000488281e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 9.059906005859375e-06s
INFO | --- Analysis for lod2-project-wiki took 3.587661027908325s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.6976444721221924s
Availability | VoID file availability check for LODAC BDLS took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.25467395782470703s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020963668823242188s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.390975952148438e-05s
Believability | Calculation of trust value for LODAC BDLS took 6.67572021484375e-06s
INFO | --- Analysis for lodac-bdls took 13.648677110671997s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.315376281738281e-05s
Availability | VoID file availability check for LODRussia Math took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.25742387771606445s
Reputation | Calculation of the PageRank for LODRussia Math took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 3.0279159545898438e-05s
Believability | Calculation of trust value for LODRussia Math took 7.62939453125e-06s
INFO | --- Analysis for lodrussia-math took 2.758777618408203s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.124641418457031e-05s
Availability | VoID file availability check for LODRussia Nano took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.26183080673217773s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.020944833755493164s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.170967102050781e-05s
Believability | Calculation of trust value for LODRussia Nano took 8.106231689453125e-06s
INFO | --- Analysis for lodrussia-nano took 2.807440757751465s
Availability | SPARQL endpoint availability check for LODStats took 4.172325134277344e-05s
Availability | VoID file availability check for LODStats took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for LODStats took 0.25258970260620117s
Reputation | Calculation of the PageRank for LODStats took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for LODStats took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for LODStats took 2.9802322387695312e-05s
Believability | Calculation of trust value for LODStats took 8.106231689453125e-06s
INFO | --- Analysis for lodstats took 2.775390625s
Availability | SPARQL endpoint availability check for LODUM took 4.1961669921875e-05s
Availability | VoID file availability check for LODUM took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for LODUM took 0.2517235279083252s
Reputation | Calculation of the PageRank for LODUM took 0.021036624908447266s
Interlinking | Calculation of Degree of Connection for LODUM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LODUM took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.075599670410156e-05s
Believability | Calculation of trust value for LODUM took 7.867813110351562e-06s
INFO | --- Analysis for lodum took 2.790552854537964s
Availability | SPARQL endpoint availability check for lofd took 0.1253952980041504s
Availability | VoID file availability check for lofd took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for lofd took 0.274486780166626s
Reputation | Calculation of the PageRank for lofd took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for lofd took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for lofd took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for lofd took 3.2901763916015625e-05s
Believability | Calculation of trust value for lofd took 7.62939453125e-06s
INFO | --- Analysis for lofd took 2.4481139183044434s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 270.42647075653076s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0011448860168457031s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2821636199951172s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.021183013916015625s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 8.106231689453125e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 1.0728836059570312e-05s
INFO | --- Analysis for loius took 584.4381809234619s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.673004150390625e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.2647061347961426s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 3.838539123535156e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 8.344650268554688e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 5.148590564727783s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.6644787788391113s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.2568833827972412s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 6.937980651855469e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.9604644775390625e-06s
INFO | --- Analysis for london-gazette took 4.059838056564331s
Availability | SPARQL endpoint availability check for Weather Stations took 4.410743713378906e-05s
Availability | VoID file availability check for Weather Stations took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.25428223609924316s
Reputation | Calculation of the PageRank for Weather Stations took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.0108642578125e-05s
Believability | Calculation of trust value for Weather Stations took 1.0013580322265625e-05s
INFO | --- Analysis for los_metar took 6.79551100730896s
Availability | SPARQL endpoint availability check for Lotico took 0.8675382137298584s
Availability | VoID file availability check for Lotico took 0.0010037422180175781s
Completeness | Calculation of interlinking completeness for Lotico took 0.681286096572876s
Reputation | Calculation of the PageRank for Lotico took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for Lotico took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.0108642578125e-05s
Believability | Calculation of trust value for Lotico took 8.344650268554688e-06s
INFO | --- Analysis for lotico took 7.049865961074829s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.21389055252075195s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0007226467132568359s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 0.2773630619049072s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 1.1435601711273193s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.14320802688598633s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.469468593597412s
Versatility | Languages check for Lower Layer Super Output Areas took 0.30722594261169434s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 0.3235335350036621s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.11586213111877441s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.14266228675842285s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.1527414321899414s
Availability | RDF dump link check for Lower Layer Super Output Areas took 48.15265703201294s
License | MR license check for Lower Layer Super Output Areas took 0.14331340789794922s
License | HR license check for Lower Layer Super Output Areas took 0.2766897678375244s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.15627408027648926s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.14783954620361328s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.33989644050598145s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.180419921875s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.19240069389343262s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.19856643676757812s
Performance | Throughput check for Lower Layer Super Output Areas took 11.282904863357544s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 7.486343383789062e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.14285635948181152s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.12040424346923828s
Interlinking | skos check for Lower Layer Super Output Areas took 0.12944293022155762s
Interlinking | skos check for Lower Layer Super Output Areas took 0.20926427841186523s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.20190072059631348s
Currency | Creation date check for Lower Layer Super Output Areas took 0.284304141998291s
Currency | Modification date check for Lower Layer Super Output Areas took 0.18010258674621582s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 0.5574746131896973s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.22122764587402344s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.144667387008667s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.14931130409240723s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.5364577770233154s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.3745458126068115s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 0.26971983909606934s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.569472074508667s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00013065338134765625s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.3079543113708496s
Security | Sign check for Lower Layer Super Output Areas took 0.309375524520874s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.2629711627960205s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.266334533691406e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 1.1920928955078125e-06s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 6.4373016357421875e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 166.52698516845703s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.38690185546875e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.27034926414489746s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0010457038879394531s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.790855407714844e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 7.62939453125e-06s
INFO | --- Analysis for lremap-auth took 2.993333101272583s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.3392181396484375e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2427675724029541s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0010213851928710938s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.409385681152344e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.0251998901367188e-05s
INFO | --- Analysis for lremap-conf took 3.417308807373047s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 5.602836608886719e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.2633066177368164s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.9087066650390625e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 6.67572021484375e-06s
INFO | --- Analysis for lremap-ri took 2.5119690895080566s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.291534423828125e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.26847290992736816s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 2.956390380859375e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.049041748046875e-05s
INFO | --- Analysis for lremap-sub took 2.546657085418701s
Availability | SPARQL endpoint availability check for LSQ took 4.3392181396484375e-05s
Availability | VoID file availability check for LSQ took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for LSQ took 0.26263952255249023s
Reputation | Calculation of the PageRank for LSQ took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.9325485229492188e-05s
Believability | Calculation of trust value for LSQ took 9.298324584960938e-06s
INFO | --- Analysis for lsq took 3.374634265899658s
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.0002644062042236328s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.24757003784179688s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0010559558868408203s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.7670135498046875e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 1.4543533325195312e-05s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.805126190185547s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.3392181396484375e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.2514991760253906s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.4809112548828125e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 7.867813110351562e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.084498643875122s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 5.364418029785156e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.23992609977722168s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 3.314018249511719e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 8.821487426757812e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.8095054626464844s
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.00026416778564453125s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.2529120445251465s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 2.9325485229492188e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 8.344650268554688e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.7791335582733154s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.315376281738281e-05s
Availability | VoID file availability check for MARC Codes List took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.2711954116821289s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020679473876953125s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00014543533325195312s
Believability | Calculation of trust value for MARC Codes List took 9.298324584960938e-06s
INFO | --- Analysis for marc-codes took 12.760494470596313s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 5.7697296142578125e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.2654080390930176s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02075791358947754s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.910064697265625e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.3113021850585938e-05s
INFO | --- Analysis for masc took 5.673857688903809s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.267692565917969e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2430579662322998s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.62396240234375e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 7.867813110351562e-06s
INFO | --- Analysis for masc-bn-nif took 2.3106350898742676s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.5990839004516602s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.24006152153015137s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.8848648071289062e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 8.344650268554688e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.125036954879761s
Availability | SPARQL endpoint availability check for medline took 4.291534423828125e-05s
Availability | VoID file availability check for medline took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for medline took 0.2481064796447754s
Reputation | Calculation of the PageRank for medline took 0.020705461502075195s
Interlinking | Calculation of Degree of Connection for medline took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for medline took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for medline took 3.528594970703125e-05s
Believability | Calculation of trust value for medline took 8.344650268554688e-06s
INFO | --- Analysis for medline took 7.9850146770477295s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 34.22131586074829s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.24169254302978516s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.021793365478515625s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 8.630752563476562e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 8.58306884765625e-06s
INFO | --- Analysis for meducator took 46.38009595870972s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.220008850097656e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.26525068283081055s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.86102294921875e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 7.62939453125e-06s
INFO | --- Analysis for mesh-finnish took 2.83524489402771s
Availability | SPARQL endpoint availability check for MeSH headings took 7.152557373046875e-05s
Availability | VoID file availability check for MeSH headings took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.25504183769226074s
Reputation | Calculation of the PageRank for MeSH headings took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 3.24249267578125e-05s
Believability | Calculation of trust value for MeSH headings took 1.1444091796875e-05s
INFO | --- Analysis for mesh_headings took 2.8134267330169678s
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.0002722740173339844s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.26941871643066406s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.0208282470703125s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.170967102050781e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 8.344650268554688e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.8303606510162354s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.2438507080078125e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2600438594818115s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020768404006958008s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0008242130279541016s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 3.0994415283203125e-05s
Believability | Calculation of trust value for MeSH pairs took 7.62939453125e-06s
INFO | --- Analysis for mesh_pairs took 2.752500534057617s
Availability | SPARQL endpoint availability check for MeSH titles took 4.124641418457031e-05s
Availability | VoID file availability check for MeSH titles took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.26012253761291504s
Reputation | Calculation of the PageRank for MeSH titles took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.147125244140625e-05s
Believability | Calculation of trust value for MeSH titles took 1.621246337890625e-05s
INFO | --- Analysis for mesh_titles took 2.829279899597168s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.291534423828125e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2506904602050781s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.170967102050781e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 6.67572021484375e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.7369837760925293s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 7.271766662597656e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.24542737007141113s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.02072429656982422s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 2.9087066650390625e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 7.62939453125e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.693080425262451s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.3392181396484375e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.2770857810974121s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.152557373046875e-05s
Believability | Calculation of trust value for MetaShare metadata model took 8.106231689453125e-06s
INFO | --- Analysis for metashare took 2.4997780323028564s
Availability | SPARQL endpoint availability check for MExiCo took 4.458427429199219e-05s
Availability | VoID file availability check for MExiCo took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2514612674713135s
Reputation | Calculation of the PageRank for MExiCo took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.8160552978515625e-05s
Believability | Calculation of trust value for MExiCo took 8.106231689453125e-06s
INFO | --- Analysis for mexico took 22.457419395446777s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 6.556510925292969e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0003349781036376953s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.26448631286621094s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.021647930145263672s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0010478496551513672s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00011491775512695312s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.559877157211304s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.649162292480469e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.2576439380645752s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010991096496582031s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.059906005859375e-06s
INFO | --- Analysis for mismuseos-gnoss took 5.132352352142334s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.08535027503967285s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2508203983306885s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.363059997558594e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 8.821487426757812e-06s
INFO | --- Analysis for mlsa took 2.7948246002197266s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.315376281738281e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.2530496120452881s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 3.0994415283203125e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 9.298324584960938e-06s
INFO | --- Analysis for mond took 2.796571731567383s
Availability | SPARQL endpoint availability check for MONDIS took 4.315376281738281e-05s
Availability | VoID file availability check for MONDIS took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for MONDIS took 0.259382963180542s
Reputation | Calculation of the PageRank for MONDIS took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for MONDIS took 3.123283386230469e-05s
Believability | Calculation of trust value for MONDIS took 9.059906005859375e-06s
INFO | --- Analysis for mondis took 2.8129029273986816s
Availability | SPARQL endpoint availability check for Monumentos took 7.033348083496094e-05s
Availability | VoID file availability check for Monumentos took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Monumentos took 0.2514660358428955s
Reputation | Calculation of the PageRank for Monumentos took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Monumentos took 4.410743713378906e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.075599670410156e-05s
Believability | Calculation of trust value for Monumentos took 9.298324584960938e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.8143270015716553s
Availability | SPARQL endpoint availability check for MORElab took 0.8826825618743896s
Availability | VoID file availability check for MORElab took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for MORElab took 0.25746750831604004s
Reputation | Calculation of the PageRank for MORElab took 0.020450592041015625s
Interlinking | Calculation of Degree of Connection for MORElab took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.678436279296875e-05s
Believability | Calculation of trust value for MORElab took 1.2636184692382812e-05s
INFO | --- Analysis for morelab took 4.591167449951172s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.79988169670105s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.26657724380493164s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02078104019165039s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.559226989746094e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.4543533325195312e-05s
INFO | --- Analysis for msc took 7.007661581039429s
Availability | SPARQL endpoint availability check for Multext-East took 4.3392181396484375e-05s
Availability | VoID file availability check for Multext-East took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Multext-East took 0.258436918258667s
Reputation | Calculation of the PageRank for Multext-East took 0.020894527435302734s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.695487976074219e-05s
Believability | Calculation of trust value for Multext-East took 8.58306884765625e-06s
INFO | --- Analysis for multext-east took 2.303884506225586s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 5.14984130859375e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.2524535655975342s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.02049994468688965s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.123283386230469e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 8.344650268554688e-06s
INFO | --- Analysis for multilingualeulaw took 2.804539918899536s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.3392181396484375e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.25342893600463867s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.021033287048339844s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.24249267578125e-05s
Believability | Calculation of trust value for Multimedia Lab took 8.821487426757812e-06s
INFO | --- Analysis for multimedia-lab took 2.3894007205963135s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 5.626678466796875e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.2594759464263916s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.147125244140625e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 8.821487426757812e-06s
INFO | --- Analysis for munich-offener-haushalt took 2.864840269088745s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.659393310546875s
Availability | VoID file availability check for Muninn World War I took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2622087001800537s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.320808410644531e-05s
Believability | Calculation of trust value for Muninn World War I took 1.0251998901367188e-05s
INFO | --- Analysis for muninn-world-war-i took 10.134055137634277s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.124641418457031e-05s
Availability | VoID file availability check for Musei Italiani took 0.00031828880310058594s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.24180316925048828s
Reputation | Calculation of the PageRank for Musei Italiani took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 2.8848648071289062e-05s
Believability | Calculation of trust value for Musei Italiani took 7.62939453125e-06s
INFO | --- Analysis for musei-italiani took 2.8305561542510986s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.57763671875e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2722790241241455s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.02069377899169922s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011324882507324219s
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 66.49630403518677s
Availability | SPARQL endpoint availability check for Italian Museums took 1.6252691745758057s
Availability | VoID file availability check for Italian Museums took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.24621295928955078s
Reputation | Calculation of the PageRank for Italian Museums took 0.021253108978271484s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.726119995117188e-05s
Believability | Calculation of trust value for Italian Museums took 8.344650268554688e-06s
INFO | --- Analysis for museums-in-italy took 4.0013017654418945s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.172325134277344e-05s
Availability | VoID file availability check for MusicBrainz took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.2487337589263916s
Reputation | Calculation of the PageRank for MusicBrainz took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.123283386230469e-05s
Believability | Calculation of trust value for MusicBrainz took 8.58306884765625e-06s
INFO | --- Analysis for musicbrainz_ took 2.7573585510253906s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.2438507080078125e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.25031423568725586s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020705461502075195s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.9087066650390625e-05s
Believability | Calculation of trust value for MusicNet Codex took 6.4373016357421875e-06s
INFO | --- Analysis for musicnet_codex took 2.800772190093994s
Availability | SPARQL endpoint availability check for myExperiment took 0.2152848243713379s
Availability | VoID file availability check for myExperiment took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for myExperiment took 0.24279451370239258s
Reputation | Calculation of the PageRank for myExperiment took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010156631469726562s
Believability | Calculation of trust value for myExperiment took 7.3909759521484375e-06s
INFO | --- Analysis for my-experiment took 3.27691650390625s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.059221744537353516s
Availability | VoID file availability check for My Family Lineage took 0.0007891654968261719s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.25780558586120605s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 0.00010204315185546875s
Believability | Calculation of trust value for My Family Lineage took 1.2159347534179688e-05s
INFO | --- Analysis for my-family-lineage took 3.7125420570373535s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 0.13962459564208984s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.2514607906341553s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02046346664428711s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.818771362304688e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for n-lex-as-linked-data took 2.570399045944214s
Availability | SPARQL endpoint availability check for NAICS 2007 took 25.65619945526123s
Availability | VoID file availability check for NAICS 2007 took 0.0008733272552490234s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.2653229236602783s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.023035526275634766s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 3.170967102050781e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0011818408966064453s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 5.078315734863281e-05s
Believability | Calculation of trust value for NAICS 2007 took 6.67572021484375e-06s
INFO | --- Analysis for naics-2007 took 124.46021699905396s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.69161057472229s
Availability | VoID file availability check for NAICS 2012 took 0.0008394718170166016s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.24912095069885254s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 6.198883056640625e-05s
Believability | Calculation of trust value for NAICS 2012 took 9.059906005859375e-06s
INFO | --- Analysis for naics-2012 took 123.42484855651855s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 1.4312536716461182s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.02131509780883789s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.459785461425781e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 9.775161743164062e-06s
INFO | --- Analysis for nalt took 3.9982569217681885s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 2.4611310958862305s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007753372192382812s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 0.9584038257598877s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 2.151235818862915s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 13.201798677444458s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 15.405502796173096s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.3195993900299072s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.809855222702026s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.7899866104125977s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.3554973602294922s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.3638622760772705s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.3518085479736328s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.36057305335998535s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.72177982330322s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.8285830020904541s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 8.26732087135315s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 1.1659889221191406s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.36076831817626953s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.3621976375579834s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.37465405464172363s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.122715473175049s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 0.00010228157043457031s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.36107397079467773s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.5011024475097656s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 2.075143814086914s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.0576894283294678s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3231544494628906s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.4798393249511719s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7126805782318115s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.943596601486206s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.32057881355285645s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.350691556930542s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3534262180328369s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.33055758476257324s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0003407001495361328s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.00048661231994628906s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.34940123558044434s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.6923396587371826s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3512601852416992s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.6125175952911377s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.273653507232666s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.668670415878296s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006546974182128906s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.32057833671569824s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.300501585006714s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.2960667610168457s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020910024642944336s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.461143493652344e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 6.4373016357421875e-06s
INFO | --- Analysis for national-diet-library-authorities took 231.92900371551514s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.35231900215148926s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006060600280761719s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 0.9008786678314209s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.7328705787658691s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.487221002578735s
Interoperability | New terms check for National Diet Library of Japan subject headings took 17.655376434326172s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.31627655029296875s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.859266996383667s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.7721221446990967s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.31890201568603516s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.35068607330322266s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.35535097122192383s
License | MR license check for National Diet Library of Japan subject headings took 0.33934760093688965s
License | HR license check for National Diet Library of Japan subject headings took 91.70330905914307s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8375685214996338s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.236316680908203s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.6897304058074951s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.3837747573852539s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.806481122970581s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3188629150390625s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.363001585006714s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 4.0531158447265625e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.3237762451171875s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.9098372459411621s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.3368945121765137s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.276092767715454s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.3616347312927246s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.0218288898468018s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.6322386264801025s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.8949024677276611s
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.35875725746154785s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.3515949249267578s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.3549633026123047s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.35869264602661133s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.00033855438232421875s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0004963874816894531s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.3173842430114746s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7139973640441895s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.32486748695373535s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.6370558738708496s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.314814805984497s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.7106785774230957s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006694793701171875s
Security | Sign check for National Diet Library of Japan subject headings took 0.35692620277404785s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 3.9395227432250977s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.3743011951446533s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.867813110351562e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 225.31896018981934s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.7422549724578857s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.71636962890625s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.291534423828125e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 7.152557373046875e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 7.8138203620910645s
Availability | SPARQL endpoint availability check for Naturopathy took 4.2438507080078125e-05s
Availability | VoID file availability check for Naturopathy took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.25801706314086914s
Reputation | Calculation of the PageRank for Naturopathy took 0.021244049072265625s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 3.314018249511719e-05s
Believability | Calculation of trust value for Naturopathy took 8.106231689453125e-06s
INFO | --- Analysis for naturopathy2 took 2.8848745822906494s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.363059997558594e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.2599668502807617s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.0517578125e-05s
Believability | Calculation of trust value for NCI Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for nci-thesaurus took 3.226123809814453s
Availability | SPARQL endpoint availability check for NDF-RT took 4.2438507080078125e-05s
Availability | VoID file availability check for NDF-RT took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.26132869720458984s
Reputation | Calculation of the PageRank for NDF-RT took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for NDF-RT took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 2.765655517578125e-05s
Believability | Calculation of trust value for NDF-RT took 6.9141387939453125e-06s
INFO | --- Analysis for ndf-rt took 2.8135695457458496s
Availability | SPARQL endpoint availability check for Near took 5.91278076171875e-05s
Availability | VoID file availability check for Near took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for Near took 0.277402400970459s
Reputation | Calculation of the PageRank for Near took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Near took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Near took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Near took 9.107589721679688e-05s
Believability | Calculation of trust value for Near took 6.9141387939453125e-06s
INFO | --- Analysis for near took 9.34685492515564s
Availability | SPARQL endpoint availability check for Neel took 4.2438507080078125e-05s
Availability | VoID file availability check for Neel took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Neel took 0.27840352058410645s
Reputation | Calculation of the PageRank for Neel took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for Neel took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neel took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Neel took 2.9087066650390625e-05s
Believability | Calculation of trust value for Neel took 9.059906005859375e-06s
INFO | --- Analysis for neel took 2.8592872619628906s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.315376281738281e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.23241186141967773s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 4.291534423828125e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 2.956390380859375e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 7.152557373046875e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.8072609901428223s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.3392181396484375e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2516622543334961s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020710468292236328s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.0517578125e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 9.775161743164062e-06s
INFO | --- Analysis for neurolex-wiki took 2.2964231967926025s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.649162292480469e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.25095486640930176s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 7.104873657226562e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 8.106231689453125e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 3.8788816928863525s
Availability | SPARQL endpoint availability check for Newsweek took 4.3392181396484375e-05s
Availability | VoID file availability check for Newsweek took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Newsweek took 0.2536458969116211s
Reputation | Calculation of the PageRank for Newsweek took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0010242462158203125s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.886222839355469e-05s
Believability | Calculation of trust value for Newsweek took 8.58306884765625e-06s
INFO | --- Analysis for newsweek took 2.779857873916626s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.482269287109375e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2774167060852051s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00011014938354492188s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for nextweb-gnoss took 9.540047645568848s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 7.534027099609375e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.26923680305480957s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020793676376342773s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.058547973632812e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 1.0728836059570312e-05s
INFO | --- Analysis for nhs-jargon took 2.671795129776001s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.267692565917969e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.2771797180175781s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.552436828613281e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 7.867813110351562e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.795482635498047s
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.0006251335144042969s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.24449443817138672s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 8.58306884765625e-06s
INFO | --- Analysis for nlr-dataset-mod took 3.7579140663146973s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.2995922565460205s
Availability | VoID file availability check for Nobel Prizes took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.25179314613342285s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.965896606445312e-05s
Believability | Calculation of trust value for Nobel Prizes took 7.3909759521484375e-06s
INFO | --- Analysis for nobelprizes took 8.161923885345459s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 30.74616241455078s
Availability | VoID file availability check for Nomenclator Asturias took 0.0008311271667480469s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2544684410095215s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 9.059906005859375e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.245208740234375e-06s
INFO | --- Analysis for nomenclator-asturias took 141.9006474018097s
Availability | SPARQL endpoint availability check for nomisma took 7.915496826171875e-05s
Availability | VoID file availability check for nomisma took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for nomisma took 0.23884129524230957s
Reputation | Calculation of the PageRank for nomisma took 0.021081209182739258s
Interlinking | Calculation of Degree of Connection for nomisma took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.123283386230469e-05s
Believability | Calculation of trust value for nomisma took 7.62939453125e-06s
INFO | --- Analysis for nomisma took 3.2469842433929443s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.3955857753753662s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.253220796585083s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0008225440979003906s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.7206878662109375e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.4066696166992188e-05s
INFO | --- Analysis for norwegian-geo-divisions took 6.161940097808838s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.220008850097656e-05s
Availability | VoID file availability check for NorwegianSoE took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.25660014152526855s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 2.956390380859375e-05s
Believability | Calculation of trust value for NorwegianSoE took 7.62939453125e-06s
INFO | --- Analysis for norwegiansoe took 2.8002872467041016s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.315376281738281e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2564430236816406s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02046489715576172s
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.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.409385681152344e-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.557299852371216s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 5.53131103515625e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2503390312194824s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.021053075790405273s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 3.314018249511719e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 9.059906005859375e-06s
INFO | --- Analysis for npg took 2.845463275909424s
Availability | SPARQL endpoint availability check for NPM took 7.390975952148438e-05s
Availability | VoID file availability check for NPM took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for NPM took 0.25241518020629883s
Reputation | Calculation of the PageRank for NPM took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for NPM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for NPM took 3.504753112792969e-05s
Believability | Calculation of trust value for NPM took 6.4373016357421875e-06s
INFO | --- Analysis for npm took 3.1106975078582764s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.014021873474121094s
Availability | VoID file availability check for NTNU special collections took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.25733470916748047s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.53131103515625e-05s
Believability | Calculation of trust value for NTNU special collections took 8.344650268554688e-06s
INFO | --- Analysis for ntnusc took 5.089796304702759s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.4345855712890625e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2510242462158203s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.822845458984375e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 5.7220458984375e-06s
INFO | --- Analysis for nuts-geovocab took 2.335460662841797s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.4166584014892578s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.2562839984893799s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.104873657226562e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 8.106231689453125e-06s
INFO | --- Analysis for nvd took 3.9460179805755615s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.6966428756713867s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.25669097900390625s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020828962326049805s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0009315013885498047s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 9.226799011230469e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 7.867813110351562e-06s
INFO | --- Analysis for nvs took 8.339364290237427s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.363059997558594e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.24184155464172363s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0001914501190185547s
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.306972026824951s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.1961669921875e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.25023317337036133s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.02121710777282715s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0008211135864257812s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.409385681152344e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 8.344650268554688e-06s
INFO | --- Analysis for o-anc took 2.7762677669525146s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.363059997558594e-05s
Availability | VoID file availability check for OANetzwerk took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.25194454193115234s
Reputation | Calculation of the PageRank for OANetzwerk took 0.0209352970123291s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.7670135498046875e-05s
Believability | Calculation of trust value for OANetzwerk took 9.059906005859375e-06s
INFO | --- Analysis for oanetzwerk took 2.84065842628479s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.363059997558594e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.27130794525146484s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 2.8133392333984375e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 8.344650268554688e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.835263967514038s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.7495326995849609s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006334781646728516s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 2.4235000610351562s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 2.4170095920562744s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 2.9022462368011475s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 4.164717197418213s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.29096865653992s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.3480849266052246s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.9272232055664062s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.4394643306732178s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5804891586303711s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.9362366199493408s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.8004813194274902s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.68623733520508s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 1.5637993812561035s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 1.4250779151916504s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 3.21907114982605s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 1.4532239437103271s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.46163177490234375s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.46791529655456543s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 16.508983373641968s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 7.867813110351562e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.6062564849853516s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.5387670993804932s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 1.2979247570037842s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 1.0907835960388184s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.5358011722564697s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 1.0266945362091064s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.4681262969970703s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.369112014770508s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 3.2282238006591797s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 1.1818068027496338s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.7475790977478027s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.9891653060913086s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.03184032440185547s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.027411460876464844s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.4171314239501953s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 14.189356327056885s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.5412213802337646s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.121459484100342s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.2643616199493408s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 14.15144157409668s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.029122114181518555s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 2.782745361328125s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.5377123355865479s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 11.526660919189453s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.7973759174346924s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02072429656982422s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010418891906738281s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 9.059906005859375e-06s
INFO | --- Analysis for ocd took 504.8533835411072s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 6.198883056640625e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.26685237884521484s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.910064697265625e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-borehole took 3.484827995300293s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.195735216140747s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.25852322578430176s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020740747451782227s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.153915405273438e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-codices took 7.000699996948242s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.0980308055877686s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.24704432487487793s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02098870277404785s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.552436828613281e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 5.9604644775390625e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 5.917171239852905s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.160703182220459s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.26450395584106445s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020923137664794922s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 7.462501525878906e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-forams took 5.883011341094971s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.1409595012664795s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.24997234344482422s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.02039027214050293s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.552436828613281e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-janus took 5.895811319351196s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 10.783433198928833s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.26874351501464844s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020631074905395508s
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.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.2901763916015625e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.1444091796875e-05s
INFO | --- Analysis for oceandrilling-janusamp took 15.193615436553955s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.139721393585205s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.26014113426208496s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020906448364257812s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 4.00543212890625e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 6.4373016357421875e-06s
INFO | --- Analysis for oceandrilling-ldeo took 5.963052272796631s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.506111145019531e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.27400851249694824s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.626678466796875e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 7.62939453125e-06s
INFO | --- Analysis for oclc-fast took 10.471129655838013s
Availability | SPARQL endpoint availability check for Open Data Communities took 5.53131103515625e-05s
Availability | VoID file availability check for Open Data Communities took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.23964142799377441s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.337860107421875e-05s
Believability | Calculation of trust value for Open Data Communities took 6.67572021484375e-06s
INFO | --- Analysis for odc took 2.7668654918670654s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.5299530029296875e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.26450419425964355s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.0517578125e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.7220458984375e-06s
INFO | --- Analysis for odc-imd-environment-score took 4.703770399093628s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.267692565917969e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.26824378967285156s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 3.0994415283203125e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 6.9141387939453125e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 2.7859208583831787s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.22977542877197266s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005209445953369141s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 0.23824238777160645s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.7373106479644775s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.16141462326049805s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.525038719177246s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.21947050094604492s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 0.2438211441040039s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.10062527656555176s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.20941448211669922s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.21235871315002441s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 62.70824098587036s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.15571951866149902s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 0.31368231773376465s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.1624925136566162s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.12794804573059082s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 1.0227901935577393s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.1374526023864746s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.1369795799255371s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.16098523139953613s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 12.15161681175232s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 7.796287536621094e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.12926077842712402s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.14623618125915527s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.584235668182373s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.14764165878295898s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.15169405937194824s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.2921617031097412s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.14982986450195312s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 0.4833548069000244s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.13950109481811523s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.1369175910949707s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.11948609352111816s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.2626972198486328s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.39216136932373047s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 0.22178196907043457s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.4846570491790771s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.00013184547424316406s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.20740151405334473s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.14743781089782715s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2428901195526123s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.245208740234375e-06s
INFO | --- Analysis for odc-lsoa took 181.41937804222107s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.3392181396484375e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2405693531036377s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020800113677978516s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 3.266334533691406e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 8.106231689453125e-06s
INFO | --- Analysis for odc-population-2005 took 3.668440103530884s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.291534423828125e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.2533690929412842s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 3.123283386230469e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 8.106231689453125e-06s
INFO | --- Analysis for ods took 2.769155263900757s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.6108171939849854s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.25505805015563965s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00010371208190917969s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for oecd-linked-data took 2.9454143047332764s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.2438507080078125e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.2698221206665039s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020992755889892578s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.2901763916015625e-05s
Believability | Calculation of trust value for Offener Haushalt took 1.4066696166992188e-05s
INFO | --- Analysis for offener-haushalt took 2.8097035884857178s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.15434455871582s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0007832050323486328s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2551860809326172s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020802974700927734s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.9591064453125e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.2636184692382812e-05s
INFO | --- Analysis for ogolod took 102.54431343078613s
Availability | SPARQL endpoint availability check for OLiA took 5.698204040527344e-05s
Availability | VoID file availability check for OLiA took 0.0007989406585693359s
Completeness | Calculation of interlinking completeness for OLiA took 0.24936580657958984s
Reputation | Calculation of the PageRank for OLiA took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for OLiA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012254714965820312s
Believability | Calculation of trust value for OLiA took 6.9141387939453125e-06s
INFO | --- Analysis for olia took 12.296087980270386s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.363059997558594e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.25403475761413574s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020891189575195312s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.0531158447265625e-05s
Believability | Calculation of trust value for OLiA Discourse took 7.867813110351562e-06s
INFO | --- Analysis for olia-discourse took 7.08720326423645s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.124641418457031e-05s
Availability | VoID file availability check for OmegaWiki took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.25180506706237793s
Reputation | Calculation of the PageRank for OmegaWiki took 0.021056652069091797s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 3.24249267578125e-05s
Believability | Calculation of trust value for OmegaWiki took 1.2636184692382812e-05s
INFO | --- Analysis for omegawiki took 2.774138927459717s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 7.221358060836792s
Availability | VoID file availability check for OntoBeef Domain took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2548079490661621s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.9591064453125e-05s
Believability | Calculation of trust value for OntoBeef Domain took 6.67572021484375e-06s
INFO | --- Analysis for ontobeef-domain took 35.16337323188782s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.458427429199219e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.24334239959716797s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.021039247512817383s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.059906005859375e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.867813110351562e-06s
INFO | --- Analysis for ontos-news-portal took 4.993837594985962s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.38690185546875e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.26465463638305664s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020653247833251953s
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.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.886222839355469e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 6.9141387939453125e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 10.14630389213562s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.267692565917969e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.24065089225769043s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 3.0517578125e-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.8235573768615723s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.935264587402344e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.25670528411865234s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.021792888641357422s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 5.078315734863281e-05s
Believability | Calculation of trust value for Open Data Euskadi took 4.76837158203125e-06s
INFO | --- Analysis for open-data-euskadi took 7.928036212921143s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 5.745887756347656e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.2658846378326416s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010323524475097656s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 8.106231689453125e-06s
INFO | --- Analysis for open-data-risp took 7.19033408164978s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.17954540252685547s
Availability | VoID file availability check for Open Data Thesaurus took 0.0005185604095458984s
Extra | Recovery of all triples for Open Data Thesaurus took 1.1382277011871338s
Performance | Total latancy measurement for Open Data Thesaurus took 0.4329094886779785s
Amount of data | Number of triples check for Open Data Thesaurus took 0.12114596366882324s
Interoperability | New terms check for Open Data Thesaurus took 1.4544098377227783s
Versatility | Languages check for Open Data Thesaurus took 0.1248636245727539s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.11098599433898926s
Security | Check HTTPS for Open Data Thesaurus took 0.29539012908935547s
Interpretability | RDF structures check for Open Data Thesaurus took 0.12746071815490723s
Versatility | Serialization formats check for Open Data Thesaurus took 0.1123056411743164s
Availability | RDF dump link check for Open Data Thesaurus took 1.045861005783081s
License | MR license check for Open Data Thesaurus took 0.11263680458068848s
License | HR license check for Open Data Thesaurus took 0.10364031791687012s
Amount of data | Number of property check for Open Data Thesaurus took 0.10384869575500488s
Understandability | Number of label check for Open Data Thesaurus took 0.10637974739074707s
Understandability | URI regex check for Open Data Thesaurus took 0.1640913486480713s
Understandability | Vocabs check for Open Data Thesaurus took 0.11106348037719727s
Verifiability | Authors check for Open Data Thesaurus took 0.12108397483825684s
Verifiability | Publishers check for Open Data Thesaurus took 0.10532474517822266s
Performance | Throughput check for Open Data Thesaurus took 10.334274291992188s
Amount of data | Check the number of entities for Open Data Thesaurus took 6.866455078125e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.10565972328186035s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.11473488807678223s
Interlinking | skos check for Open Data Thesaurus took 0.10539579391479492s
Interlinking | skos check for Open Data Thesaurus took 0.08125901222229004s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.09793305397033691s
Currency | Creation date check for Open Data Thesaurus took 0.1630873680114746s
Currency | Modification date check for Open Data Thesaurus took 0.2089550495147705s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4185004234313965s
Interoperability | New vocabularies check for Open Data Thesaurus took 0.9099435806274414s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.10505557060241699s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.09990787506103516s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.09959578514099121s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.17315292358398438s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011813640594482422s
Consistency | Disjoint class check for Open Data Thesaurus took 0.07727527618408203s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.20126557350158691s
Consistency | Misplaced classes for Open Data Thesaurus took 0.0855855941772461s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.507279396057129s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.3921575546264648s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0006320476531982422s
Security | Sign check for Open Data Thesaurus took 0.0982980728149414s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.24485993385314941s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020090341567993164s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 9.012222290039062e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.5051984786987305s
Believability | Calculation of trust value for Open Data Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for open-data-thesaurus took 41.75768518447876s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.482269287109375e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.24979472160339355s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 3.0279159545898438e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 7.3909759521484375e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.7425408363342285s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.38690185546875e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.2608189582824707s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.02076435089111328s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.937980651855469e-05s
Believability | Calculation of trust value for Open Election Data Project took 5.245208740234375e-06s
INFO | --- Analysis for open-election-data-project took 2.911530017852783s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.633836030960083s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.2603945732116699s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0011148452758789062s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 0.000110626220703125s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 6.4373016357421875e-06s
INFO | --- Analysis for open-energy-info-wiki took 10.390491962432861s
Availability | SPARQL endpoint availability check for Open Library took 4.458427429199219e-05s
Availability | VoID file availability check for Open Library took 0.0008723735809326172s
Completeness | Calculation of interlinking completeness for Open Library took 0.2880072593688965s
Reputation | Calculation of the PageRank for Open Library took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for Open Library took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.224082946777344e-05s
Believability | Calculation of trust value for Open Library took 8.821487426757812e-06s
INFO | --- Analysis for open-library took 9.491399049758911s
Availability | SPARQL endpoint availability check for Open Directory took 4.2438507080078125e-05s
Availability | VoID file availability check for Open Directory took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Open Directory took 0.2676405906677246s
Reputation | Calculation of the PageRank for Open Directory took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.170967102050781e-05s
Believability | Calculation of trust value for Open Directory took 1.4543533325195312e-05s
INFO | --- Analysis for open_directory took 2.858030080795288s
Availability | SPARQL endpoint availability check for flyatlas took 4.202409267425537s
Availability | VoID file availability check for flyatlas took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for flyatlas took 0.2599177360534668s
Reputation | Calculation of the PageRank for flyatlas took 0.02075338363647461s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.075599670410156e-05s
Believability | Calculation of trust value for flyatlas took 7.3909759521484375e-06s
INFO | --- Analysis for openbiomed-flyatlas took 12.072522401809692s
Availability | SPARQL endpoint availability check for OpenCalais took 4.410743713378906e-05s
Availability | VoID file availability check for OpenCalais took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2559175491333008s
Reputation | Calculation of the PageRank for OpenCalais took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010967254638671875s
Believability | Calculation of trust value for OpenCalais took 1.2636184692382812e-05s
INFO | --- Analysis for opencalais took 4.386294603347778s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 5.555152893066406e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.24809789657592773s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.367134094238281e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 6.67572021484375e-06s
INFO | --- Analysis for opencorporates took 2.6277523040771484s
Availability | SPARQL endpoint availability check for OpenCyc took 4.4345855712890625e-05s
Availability | VoID file availability check for OpenCyc took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2500576972961426s
Reputation | Calculation of the PageRank for OpenCyc took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010561943054199219s
Believability | Calculation of trust value for OpenCyc took 6.67572021484375e-06s
INFO | --- Analysis for opencyc took 2.2530808448791504s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.2551703453063965s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.02078843116760254s
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.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.528594970703125e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 4.015733242034912s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.2572774887084961s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.0813095569610596s
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.0011229515075683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.26964759826660156s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020740985870361328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.7670135498046875e-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 3.8155486583709717s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00032329559326171875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2553377151489258s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.282381772994995s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.27504587173461914s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.138554096221924s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0003876686096191406s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.26949071884155273s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 4.740788459777832s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.2576725482940674s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 3.594623327255249s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.23870372772216797s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.2782065868377686s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007681846618652344s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.2582058906555176s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.073796510696411s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.26329898834228516s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 6.008148193359375e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 3.0479331016540527s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2585783004760742s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.02074432373046875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.172325134277344e-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.887024402618408s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.24476861953735352s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020955324172973633s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.0829341411590576s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.6253204345703125e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.24548625946044922s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.9803969860076904s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 7.319450378417969e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.2525339126586914s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.290548324584961s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.25137948989868164s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02117609977722168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 5.221366882324219e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.9351794719696045s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.9591064453125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.27291202545166016s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 4.345367908477783s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.696846008300781e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.2680366039276123s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.021112918853759766s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0009002685546875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.9102110862731934s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.7206878662109375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2674703598022461s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.220008850097656e-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 3.079299211502075s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0003502368927001953s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2579345703125s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.022346973419189453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0008082389831542969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.282562494277954s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 5.650520324707031e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0003752708435058594s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.25396299362182617s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02103257179260254s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0010273456573486328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 5.030632019042969e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.0780718326568604s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0003705024719238281s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.24114990234375s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.8147008419036865s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 5.745887756347656e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2630188465118408s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020936250686645508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.430511474609375e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 3.764220714569092s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007522106170654297s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.24031949043273926s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.146910190582275s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.2625608444213867s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 3.844442129135132s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.25315284729003906s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.5410656929016113s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2806277275085449s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 3.5864481925964355s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007939338684082031s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.24684691429138184s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.208012819290161s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.2519378662109375s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 3.7080893516540527s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007669925689697266s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.2558324337005615s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.532057046890259s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.6253204345703125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.25400471687316895s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020822525024414062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.4111528396606445s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0008244514465332031s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2635958194732666s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020944833755493164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.671760082244873s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 7.271766662597656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2624640464782715s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007646083831787109s
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 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.592556715011597s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 8.559226989746094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2615087032318115s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.7112767696380615s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.9591064453125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.25283312797546387s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.252798080444336s
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.00023865699768066406s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.23902559280395508s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.2248568534851074s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2405986785888672s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 5.412101745605469e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.477334499359131s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.00038433074951171875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2593879699707031s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020684003829956055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.3755998611450195s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.25400233268737793s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020838260650634766s
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.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 3.9605677127838135s
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.0005905628204345703s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2625765800476074s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.910182237625122s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 5.650520324707031e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.25932836532592773s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020586252212524414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 3.562263011932373s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0003273487091064453s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.2520127296447754s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.8918488025665283s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.26392221450805664s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007808208465576172s
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 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.8271496295928955s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.27187275886535645s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 3.8828883171081543s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 5.852695941925049s
Availability | VoID file availability check for Open Data of Ecuador took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2679555416107178s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.821487426757812e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.239776611328125e-05s
INFO | --- Analysis for opendataec took 10.892849445343018s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2706160545349121s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 6.67572021484375e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.50183367729187s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.23820018768310547s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.708620548248291s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.24076628684997559s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020854711532592773s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.5743215084075928s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.26581907272338867s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0008275508880615234s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.6293466091156006s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.601478576660156e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.2591545581817627s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02083420753479004s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 8.821487426757812e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.6489453315734863s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 7.700920104980469e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.24660634994506836s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.60750150680542s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.458427429199219e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.24467015266418457s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020748376846313477s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 6.67572021484375e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.630218029022217s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.506111145019531e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2671027183532715s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.02100825309753418s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.6365556716918945s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.25041961669921875s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02064204216003418s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 6.4373016357421875e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.2983450889587402s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.50729465484619s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00040030479431152344s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.25701069831848145s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.02182602882385254s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 4.100799560546875e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.2636184692382812e-05s
INFO | --- Analysis for openlink-lod-cache took 62.81650400161743s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.5299530029296875e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.25294971466064453s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.012222290039062e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 5.9604644775390625e-06s
INFO | --- Analysis for openlylocal took 8.272036790847778s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 0.7617213726043701s
Availability | VoID file availability check for OpenMobileNetwork took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.26531386375427246s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02099895477294922s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 8.630752563476562e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 8.58306884765625e-06s
INFO | --- Analysis for openmobilenetwork took 3.371549129486084s
Availability | SPARQL endpoint availability check for OpenTox took 4.3392181396484375e-05s
Availability | VoID file availability check for OpenTox took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for OpenTox took 0.2507288455963135s
Reputation | Calculation of the PageRank for OpenTox took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.1948089599609375e-05s
Believability | Calculation of trust value for OpenTox took 9.059906005859375e-06s
INFO | --- Analysis for opentox took 2.8279318809509277s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.9114227294921875e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.25896334648132324s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.123283386230469e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for openuplabs took 2.803058624267578s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.4345855712890625e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.2531602382659912s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020993471145629883s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 3.361701965332031e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 6.9141387939453125e-06s
INFO | --- Analysis for opus took 2.8537962436676025s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 4.410743713378906e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.000274658203125s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.27552199363708496s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.600120544433594e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 8.821487426757812e-06s
INFO | --- Analysis for orcid took 2.8731977939605713s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.0111188888549805s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2534210681915283s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.0001163482666015625s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.8358230590820312e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 5.715392827987671s
Availability | SPARQL endpoint availability check for oreilly took 0.0001163482666015625s
Availability | VoID file availability check for oreilly took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for oreilly took 0.25220346450805664s
Reputation | Calculation of the PageRank for oreilly took 0.02186131477355957s
Interlinking | Calculation of Degree of Connection for oreilly took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0010571479797363281s
Interlinking | Calculation of Clustering coefficient for oreilly took 6.198883056640625e-05s
Believability | Calculation of trust value for oreilly took 8.344650268554688e-06s
INFO | --- Analysis for oreilly took 4.844108581542969s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.061867475509643555s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.25629544258117676s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020824432373046875s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.67572021484375e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for organic-edunet took 8.630068302154541s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.786407947540283s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.24691438674926758s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.021175861358642578s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.320808410644531e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 8.344650268554688e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 28.955188035964966s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.4565505981445312s
Availability | VoID file availability check for OSM Semantic Network took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2531588077545166s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.743171691894531e-05s
Believability | Calculation of trust value for OSM Semantic Network took 8.821487426757812e-06s
INFO | --- Analysis for osm-semantic-network took 8.011242628097534s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.267692565917969e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.24975872039794922s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 2.9087066650390625e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 8.58306884765625e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 2.7958526611328125s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.649162292480469e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.2565653324127197s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020758867263793945s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 8.344650268554688e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 2.7866621017456055s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.172325134277344e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.23728156089782715s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.361701965332031e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.0967254638671875e-05s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 2.824984550476074s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.38690185546875e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.2585475444793701s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 9.298324584960938e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 2.8277153968811035s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.1961669921875e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.26673436164855957s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020923376083374023s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 3.24249267578125e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 1.811981201171875e-05s
INFO | --- Analysis for ox-ac-uk-timeseries took 2.753894805908203s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.1961669921875e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.25098729133605957s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 3.24249267578125e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 9.298324584960938e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.7682344913482666s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 8.273124694824219e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2485496997833252s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.02086615562438965s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.123283386230469e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 8.344650268554688e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.726940631866455s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.2438507080078125e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2402184009552002s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020837068557739258s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 3.361701965332031e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 8.821487426757812e-06s
INFO | --- Analysis for oxpoints took 2.7689805030822754s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.6182043552398682s
Availability | VoID file availability check for Pali English Lexicon took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.24544548988342285s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.218650817871094e-05s
Believability | Calculation of trust value for Pali English Lexicon took 9.059906005859375e-06s
INFO | --- Analysis for pali-english-lexicon took 6.526589393615723s
Availability | SPARQL endpoint availability check for PanLex took 1.0695855617523193s
Availability | VoID file availability check for PanLex took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for PanLex took 0.2513456344604492s
Reputation | Calculation of the PageRank for PanLex took 0.020914793014526367s
Interlinking | Calculation of Degree of Connection for PanLex took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for PanLex took 8.130073547363281e-05s
Believability | Calculation of trust value for PanLex took 6.9141387939453125e-06s
INFO | --- Analysis for panlex took 5.275988817214966s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.050559282302856445s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.255169153213501s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.9591064453125e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.3592512607574463s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.410743713378906e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.267197847366333s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.981590270996094e-05s
Believability | Calculation of trust value for PDEV-Lemon took 6.198883056640625e-06s
INFO | --- Analysis for pdev-lemon took 3.6997835636138916s
Availability | SPARQL endpoint availability check for pdevlemon took 4.38690185546875e-05s
Availability | VoID file availability check for pdevlemon took 0.0013294219970703125s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.24248576164245605s
Reputation | Calculation of the PageRank for pdevlemon took 0.020926475524902344s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.0279159545898438e-05s
Believability | Calculation of trust value for pdevlemon took 6.9141387939453125e-06s
INFO | --- Analysis for pdevlemon took 3.042280673980713s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.291534423828125e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008893013000488281s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.25601649284362793s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020911455154418945s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.654594421386719e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.1682510375976562e-05s
INFO | --- Analysis for periodo took 17.888372898101807s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.363059997558594e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.2557358741760254s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0003941059112548828s
Believability | Calculation of trust value for Personal_Homepages took 7.62939453125e-06s
INFO | --- Analysis for personal-homepages took 2.2771708965301514s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0576224327087402s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.254256010055542s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.62396240234375e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 8.821487426757812e-06s
INFO | --- Analysis for phoible took 4.6375203132629395s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.4345855712890625e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2708303928375244s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.58306884765625e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 8.58306884765625e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.3320348262786865s
Availability | SPARQL endpoint availability check for Pleiades took 4.38690185546875e-05s
Availability | VoID file availability check for Pleiades took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Pleiades took 0.2641315460205078s
Reputation | Calculation of the PageRank for Pleiades took 0.020833730697631836s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.273124694824219e-05s
Believability | Calculation of trust value for Pleiades took 6.67572021484375e-06s
INFO | --- Analysis for pleiades took 12.451981544494629s
Availability | SPARQL endpoint availability check for Poképédia took 4.673004150390625e-05s
Availability | VoID file availability check for Poképédia took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Poképédia took 0.24923014640808105s
Reputation | Calculation of the PageRank for Poképédia took 0.021387100219726562s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Poképédia took 8.20159912109375e-05s
Believability | Calculation of trust value for Poképédia took 9.775161743164062e-06s
INFO | --- Analysis for pokepedia-fr took 2.5299527645111084s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.38690185546875e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.23960566520690918s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.028475046157836914s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0008358955383300781s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.00010728836059570312s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0013580322265625e-05s
INFO | --- Analysis for polymath-virtual-library took 5.787821054458618s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.410743713378906e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.26583051681518555s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.02120041847229004s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.361701965332031e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 6.4373016357421875e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.769883155822754s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.410743713378906e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.25926899909973145s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.021299362182617188s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 3.337860107421875e-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.8004326820373535s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 4.2438507080078125e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.26764607429504395s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.021037578582763672s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0011341571807861328s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 4.220008850097656e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 9.298324584960938e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.8715364933013916s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.649162292480469e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.27049732208251953s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.02099299430847168s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0011031627655029297s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.981590270996094e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 8.58306884765625e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.8272762298583984s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2589395046234131s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020854711532592773s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.266334533691406e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 9.059906005859375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.8973171710968018s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.410743713378906e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.25103187561035156s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.02166295051574707s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0008909702301025391s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.719329833984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.816936492919922s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.2420825958251953s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.020615100860595703s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 3.147125244140625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.8001768589019775s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.363059997558594e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.26082873344421387s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.02085733413696289s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.075599670410156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.780392646789551s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.26209449768066406s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020558595657348633s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 8.344650268554688e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.8246028423309326s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2609851360321045s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 9.059906005859375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.7838294506073s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0008087158203125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2478351593017578s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 2.86102294921875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.7825264930725098s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.3392181396484375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.25813722610473633s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.021037578582763672s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 5.1975250244140625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.7953262329101562s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2523829936981201s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.8152902126312256s
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.0005705356597900391s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2633960247039795s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.021707534790039062s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.361701965332031e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 8.821487426757812e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.8022732734680176s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2595212459564209s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.021018266677856445s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 3.218650817871094e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.8054819107055664s
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.0002474784851074219s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2804274559020996s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.020984649658203125s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 3.314018249511719e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.8934996128082275s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 7.224082946777344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.2540733814239502s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020750999450683594s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.218650817871094e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.7259931564331055s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.315376281738281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2744112014770508s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.0208892822265625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.790433168411255s
Availability | SPARQL endpoint availability check for prefix.cc took 4.3392181396484375e-05s
Availability | VoID file availability check for prefix.cc took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.24309420585632324s
Reputation | Calculation of the PageRank for prefix.cc took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.838539123535156e-05s
Believability | Calculation of trust value for prefix.cc took 7.62939453125e-06s
INFO | --- Analysis for prefix-cc took 3.4133694171905518s
Availability | SPARQL endpoint availability check for PreLex took 0.11441922187805176s
Availability | VoID file availability check for PreLex took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for PreLex took 0.25396203994750977s
Reputation | Calculation of the PageRank for PreLex took 0.020945072174072266s
Interlinking | Calculation of Degree of Connection for PreLex took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.796287536621094e-05s
Believability | Calculation of trust value for PreLex took 9.775161743164062e-06s
INFO | --- Analysis for prelex took 2.6297407150268555s
Availability | SPARQL endpoint availability check for Prelinger Archives took 1.7124497890472412s
Availability | VoID file availability check for Prelinger Archives took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.26453304290771484s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.24249267578125e-05s
Believability | Calculation of trust value for Prelinger Archives took 8.821487426757812e-06s
INFO | --- Analysis for prelinger_archives took 9.425097465515137s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.45360875129699707s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0006806850433349609s
Extra | Recovery of all triples for PreMOn (Predicate Model for Ontologies) took 3.5837998390197754s
Performance | Total latancy measurement for PreMOn (Predicate Model for Ontologies) took 1.4405946731567383s
Amount of data | Number of triples check for PreMOn (Predicate Model for Ontologies) took 0.0952751636505127s
Interoperability | New terms check for PreMOn (Predicate Model for Ontologies) took 2.301588535308838s
Versatility | Languages check for PreMOn (Predicate Model for Ontologies) took 58.58351993560791s
Interpretability | Number of blank nodes check for PreMOn (Predicate Model for Ontologies) took 0.10960698127746582s
Security | Check HTTPS for PreMOn (Predicate Model for Ontologies) took 0.08442997932434082s
Interpretability | RDF structures check for PreMOn (Predicate Model for Ontologies) took 0.19721388816833496s
Versatility | Serialization formats check for PreMOn (Predicate Model for Ontologies) took 0.24022388458251953s
Availability | RDF dump link check for PreMOn (Predicate Model for Ontologies) took 0.2107224464416504s
License | MR license check for PreMOn (Predicate Model for Ontologies) took 0.3829171657562256s
License | HR license check for PreMOn (Predicate Model for Ontologies) took 0.9444866180419922s
Amount of data | Number of property check for PreMOn (Predicate Model for Ontologies) took 0.282865047454834s
Understandability | Number of label check for PreMOn (Predicate Model for Ontologies) took 0.09437346458435059s
Understandability | URI regex check for PreMOn (Predicate Model for Ontologies) took 0.43692708015441895s
Understandability | Vocabs check for PreMOn (Predicate Model for Ontologies) took 0.4792308807373047s
Verifiability | Authors check for PreMOn (Predicate Model for Ontologies) took 0.2716808319091797s
Verifiability | Publishers check for PreMOn (Predicate Model for Ontologies) took 0.2927734851837158s
Performance | Throughput check for PreMOn (Predicate Model for Ontologies) took 11.605280876159668s
Amount of data | Check the number of entities for PreMOn (Predicate Model for Ontologies) took 3.409385681152344e-05s
Verifiability | Contribs. check for PreMOn (Predicate Model for Ontologies) took 0.37865161895751953s
Interlinking | sameAs chians check for PreMOn (Predicate Model for Ontologies) took 0.38132143020629883s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.48078346252441406s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.36588382720947266s
Timeliness | dataset update frequency check for PreMOn (Predicate Model for Ontologies) took 0.38942837715148926s
Currency | Creation date check for PreMOn (Predicate Model for Ontologies) took 1.8488147258758545s
Currency | Modification date check for PreMOn (Predicate Model for Ontologies) took 0.7678287029266357s
Rep.Conc. | URIs length for PreMOn (Predicate Model for Ontologies) took 3.9032421112060547s
Interoperability | New vocabularies check for PreMOn (Predicate Model for Ontologies) took 5.4836273193359375e-06s
Consistency | Deprecated classes/propertiers check for PreMOn (Predicate Model for Ontologies) took 0.20498132705688477s
Accuracy | Check Empty annotation labels for PreMOn (Predicate Model for Ontologies) took 1.351391077041626s
Accuracy | Check White space in annotation for PreMOn (Predicate Model for Ontologies) took 0.08423113822937012s
Accuracy | Check Datatype consistency for PreMOn (Predicate Model for Ontologies) took 0.0833890438079834s
Consistency | Disjoint class check for PreMOn (Predicate Model for Ontologies) took 0.19855141639709473s
Consistency | Check Misplaced properties for PreMOn (Predicate Model for Ontologies) took 2.1133475303649902s
Consistency | Misplaced classes for PreMOn (Predicate Model for Ontologies) took 1.484598159790039s
Consistency | Check Ontology hijacking for PreMOn (Predicate Model for Ontologies) took 2.401013135910034s
Consistency | Check Invalid usage of undefined classes for PreMOn (Predicate Model for Ontologies) took 1.3123857975006104s
Consistency | Check Invalid usage of undefined properties for PreMOn (Predicate Model for Ontologies) took 3.0332531929016113s
Conciseness | Check Extensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.08884072303771973s
Conciseness | Check Intensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.2343440055847168s
Security | Sign check for PreMOn (Predicate Model for Ontologies) took 0.22690463066101074s
Availability | Check URIs Dereferenciability for PreMOn (Predicate Model for Ontologies) took 1163.4524862766266s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.9911971092224121s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.021771907806396484s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn (Predicate Model for Ontologies) took 1.430511474609375e-06s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 8.106231689453125e-06s
INFO | --- Analysis for premon took 1292.0971286296844s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 8.535385131835938e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.24957537651062012s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020789384841918945s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.650520324707031e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 8.106231689453125e-06s
INFO | --- Analysis for princeton-library-findingaids took 6.672903299331665s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.5461583137512207s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.25820136070251465s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.987022399902344e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.106231689453125e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.2925338745117188s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 5.602836608886719e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.27179908752441406s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 2.8133392333984375e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 7.3909759521484375e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 3.331920623779297s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.315376281738281e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.2519958019256592s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.0517578125e-05s
Believability | Calculation of trust value for Procomún SPARQL took 8.58306884765625e-06s
INFO | --- Analysis for procomun-sparql took 2.7587392330169678s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.458427429199219e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.2807316780090332s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 9.059906005859375e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.781761407852173s
Availability | SPARQL endpoint availability check for ProductDB took 0.04969620704650879s
Availability | VoID file availability check for ProductDB took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2556731700897217s
Reputation | Calculation of the PageRank for ProductDB took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for ProductDB took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ProductDB took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for ProductDB took 9.679794311523438e-05s
Believability | Calculation of trust value for ProductDB took 1.0013580322265625e-05s
INFO | --- Analysis for productdb took 2.362558126449585s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2673521041870117s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.796287536621094e-05s
Believability | Calculation of trust value for Product Types Ontology took 8.58306884765625e-06s
INFO | --- Analysis for productontology took 3.1982920169830322s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.601478576660156e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.251251220703125s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010180473327636719s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 9.236680746078491s
Availability | SPARQL endpoint availability check for provenanceweb took 0.044943809509277344s
Availability | VoID file availability check for provenanceweb took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.26717567443847656s
Reputation | Calculation of the PageRank for provenanceweb took 0.021094560623168945s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.843971252441406e-05s
Believability | Calculation of trust value for provenanceweb took 9.775161743164062e-06s
INFO | --- Analysis for provenanceweb took 47.32127833366394s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.6253204345703125e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2448723316192627s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 9.822845458984375e-05s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 7.867813110351562e-06s
INFO | --- Analysis for proyectoapadrina took 7.583760976791382s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 26.75610327720642s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008819103240966797s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.25817441940307617s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.62396240234375e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 5.245208740234375e-06s
INFO | --- Analysis for pscs-catalogue took 125.9084861278534s
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.0006067752838134766s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.24220824241638184s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.021077632904052734s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.939338684082031e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 8.344650268554688e-06s
INFO | --- Analysis for psh-subject-headings took 3.2389516830444336s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.38690185546875e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.25062084197998047s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 2.956390380859375e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.821892499923706s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.6890459060668945s
Availability | VoID file availability check for Public Spending in Greece took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.2534511089324951s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.106231689453125e-05s
Believability | Calculation of trust value for Public Spending in Greece took 8.344650268554688e-06s
INFO | --- Analysis for public-spending-in-greece took 8.420052289962769s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.6253204345703125e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00036144256591796875s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.2660539150238037s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 3.24249267578125e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 8.344650268554688e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.8757834434509277s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.2438507080078125e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.24476957321166992s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.24249267578125e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 8.344650268554688e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 2.7721545696258545s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.458427429199219e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.24594855308532715s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 3.0517578125e-05s
Believability | Calculation of trust value for qualitywebdata.org took 8.821487426757812e-06s
INFO | --- Analysis for qualitywebdata-org took 2.727179765701294s
Availability | SPARQL endpoint availability check for Quotations Book took 4.4345855712890625e-05s
Availability | VoID file availability check for Quotations Book took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.2573058605194092s
Reputation | Calculation of the PageRank for Quotations Book took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 2.9802322387695312e-05s
Believability | Calculation of trust value for Quotations Book took 1.9550323486328125e-05s
INFO | --- Analysis for quotations_book took 2.805948495864868s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2594611644744873s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.021701812744140625s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.5762786865234375e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 9.298324584960938e-06s
INFO | --- Analysis for r4r took 2.818934202194214s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.1970500946044922s
Availability | VoID file availability check for Rådata nå! took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.26738452911376953s
Reputation | Calculation of the PageRank for Rådata nå! took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.392333984375e-05s
Believability | Calculation of trust value for Rådata nå! took 8.58306884765625e-06s
INFO | --- Analysis for radatana took 4.367471694946289s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.506111145019531e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0008304119110107422s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.2680039405822754s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 4.601478576660156e-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.535571336746216s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.2438507080078125e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.24182844161987305s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.0994415283203125e-05s
Believability | Calculation of trust value for Raphael Research Resource took 8.106231689453125e-06s
INFO | --- Analysis for raphaelresearchresource took 2.7667582035064697s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.628034353256226s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.33032822608947754s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02106451988220215s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.647804260253906e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 7.3909759521484375e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 27.095864295959473s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.7206878662109375e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.24167275428771973s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.02071237564086914s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 2.785738945007324s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.2579340934753418s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.022078514099121094s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.337860107421875e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 2.7922940254211426s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.2505159378051758s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.1948089599609375e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 2.85835337638855s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.25072693824768066s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 9.5367431640625e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 2.7945072650909424s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.267692565917969e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.26784324645996094s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 2.7894973754882812e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 7.152557373046875e-06s
INFO | --- Analysis for rcahmw-periods-list took 2.7869741916656494s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.410743713378906e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2784121036529541s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 0.00010347366333007812s
Believability | Calculation of trust value for RDF Book Mashup took 7.152557373046875e-06s
INFO | --- Analysis for rdf-book-mashup took 3.0967817306518555s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.410743713378906e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.24912548065185547s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 9.965896606445312e-05s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 7.3909759521484375e-06s
INFO | --- Analysis for rdfize-lastfm took 2.31059193611145s
Availability | SPARQL endpoint availability check for RDFLicense took 261.27968859672546s
Availability | VoID file availability check for RDFLicense took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.26145076751708984s
Reputation | Calculation of the PageRank for RDFLicense took 0.02067279815673828s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.790855407714844e-05s
Believability | Calculation of trust value for RDFLicense took 8.58306884765625e-06s
INFO | --- Analysis for rdflicense took 536.2136051654816s
Availability | SPARQL endpoint availability check for RDFohloh took 4.4345855712890625e-05s
Availability | VoID file availability check for RDFohloh took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.7116594314575195s
Reputation | Calculation of the PageRank for RDFohloh took 0.020771026611328125s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.942054748535156e-05s
Believability | Calculation of trust value for RDFohloh took 7.152557373046875e-06s
INFO | --- Analysis for rdfohloh took 8.164461612701416s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.539680004119873s
Availability | VoID file availability check for Reactome RDF took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.2508847713470459s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0010688304901123047s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 4.5299530029296875e-05s
Believability | Calculation of trust value for Reactome RDF took 7.867813110351562e-06s
INFO | --- Analysis for reactome-rdf took 3.935486316680908s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.1445786952972412s
Availability | VoID file availability check for Rechtspraak.nl took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.24730396270751953s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.489059448242188e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 5.9604644775390625e-06s
INFO | --- Analysis for rechtspraak took 2.5184762477874756s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.482269287109375e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2793745994567871s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.797645568847656e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 6.67572021484375e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 6.840809345245361s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.029833555221557617s
Availability | VoID file availability check for reference.data.gov.uk took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2790801525115967s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015997886657714844s
Believability | Calculation of trust value for reference.data.gov.uk took 5.9604644775390625e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.4685065746307373s
Availability | SPARQL endpoint availability check for Regiony took 4.267692565917969e-05s
Availability | VoID file availability check for Regiony took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for Regiony took 0.2587404251098633s
Reputation | Calculation of the PageRank for Regiony took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Regiony took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Regiony took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.147125244140625e-05s
Believability | Calculation of trust value for Regiony took 1.52587890625e-05s
INFO | --- Analysis for regiony took 2.809258222579956s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.20075297355651855s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.3248167037963867s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02064061164855957s
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.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 3.933906555175781e-05s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 8.106231689453125e-06s
INFO | --- Analysis for reload took 13.707767486572266s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.4039130210876465s
Availability | VoID file availability check for Renewable Energy Generators took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.2565639019012451s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0008497238159179688s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.744529724121094e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 1.0013580322265625e-05s
INFO | --- Analysis for renewable_energy_generators took 9.560729265213013s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.029990673065185547s
Availability | VoID file availability check for research.data.gov.uk took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.26493358612060547s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020711421966552734s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 8.893013000488281e-05s
Believability | Calculation of trust value for research.data.gov.uk took 4.5299530029296875e-06s
INFO | --- Analysis for research-data-gov-uk took 2.3544762134552s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 4.2438507080078125e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.25258398056030273s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020412445068359375s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007696151733398438s
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 8.344650268554688e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 2.8417160511016846s
Availability | SPARQL endpoint availability check for Restaurantes took 4.839897155761719e-05s
Availability | VoID file availability check for Restaurantes took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.28231358528137207s
Reputation | Calculation of the PageRank for Restaurantes took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for Restaurantes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Restaurantes took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 2.9087066650390625e-05s
Believability | Calculation of trust value for Restaurantes took 8.344650268554688e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.875427484512329s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 0.00010704994201660156s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.267702579498291s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.747245788574219e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 7.3909759521484375e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 3.8217010498046875s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.15504837036132812s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2528395652770996s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011968612670898438s
Believability | Calculation of trust value for Revyu.com - Review Anything took 8.821487426757812e-06s
INFO | --- Analysis for revyu took 2.495696783065796s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.363059997558594e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.2414412498474121s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020682096481323242s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.8160552978515625e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 7.867813110351562e-06s
INFO | --- Analysis for riese took 2.4581105709075928s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.291534423828125e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0003478527069091797s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.26589179039001465s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.02114582061767578s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.170967102050781e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 8.106231689453125e-06s
INFO | --- Analysis for rijksmuseum took 2.8253536224365234s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.5756819248199463s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.2532796859741211s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.6253204345703125e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 7.867813110351562e-06s
INFO | --- Analysis for rism took 3.5133495330810547s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.192488431930542s
Availability | VoID file availability check for RISM Authority data took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.2624666690826416s
Reputation | Calculation of the PageRank for RISM Authority data took 0.02102947235107422s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.649162292480469e-05s
Believability | Calculation of trust value for RISM Authority data took 8.58306884765625e-06s
INFO | --- Analysis for rism-authorities took 3.142699718475342s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.03738713264465332s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.2583122253417969s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002307891845703125s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.4109036922454834s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.026518583297729492s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.2745063304901123s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02082991600036621s
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.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001418590545654297s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.3989620208740234s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.04317426681518555s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.24335336685180664s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00020122528076171875s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.3340306282043457s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.04054665565490723s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2497696876525879s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00015974044799804688s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.376293897628784s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.03905177116394043s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.24712276458740234s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.0001583099365234375s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-courseware took 2.319979190826416s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.03694462776184082s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2584531307220459s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.814697265625e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 5.245208740234375e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.3907341957092285s
Availability | SPARQL endpoint availability check for crm took 4.4345855712890625e-05s
Availability | VoID file availability check for crm took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for crm took 0.2497565746307373s
Reputation | Calculation of the PageRank for crm took 0.02095198631286621s
Interlinking | Calculation of Degree of Connection for crm took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for crm took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for crm took 3.123283386230469e-05s
Believability | Calculation of trust value for crm took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.8839926719665527s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0370182991027832s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0003795623779296875s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.26247620582580566s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.000118255615234375s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.314800500869751s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.03394150733947754s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0003628730773925781s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.2623157501220703s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.221366882324219e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.3454418182373047s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.03599429130554199s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0003376007080078125s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.2611076831817627s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00023651123046875s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.3472158908843994s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.03766751289367676s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00020551681518554688s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.2539181709289551s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.510185241699219e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.2852749824523926s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.03348588943481445s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.26304006576538086s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.894371032714844e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.3554983139038086s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.040845394134521484s
Availability | VoID file availability check for digitaleconomy took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.26105785369873047s
Reputation | Calculation of the PageRank for digitaleconomy took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.9802322387695312e-05s
Believability | Calculation of trust value for digitaleconomy took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.3674252033233643s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.04307675361633301s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.25514721870422363s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.021106719970703125s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00015044212341308594s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.3363308906555176s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.03195667266845703s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2446146011352539s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.506111145019531e-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.5739824771881104s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.458427429199219e-05s
Availability | VoID file availability check for enaktingpsi took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.2504279613494873s
Reputation | Calculation of the PageRank for enaktingpsi took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 3.147125244140625e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 3.528594970703125e-05s
Believability | Calculation of trust value for enaktingpsi took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.777099609375s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.050191640853881836s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.24232006072998047s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0001823902130126953s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.3493523597717285s
Availability | SPARQL endpoint availability check for epsrc took 0.04226422309875488s
Availability | VoID file availability check for epsrc took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for epsrc took 0.2611825466156006s
Reputation | Calculation of the PageRank for epsrc took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.936622619628906e-05s
Believability | Calculation of trust value for epsrc took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.366184711456299s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.034796953201293945s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.25359487533569336s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.700920104980469e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-era took 2.3299450874328613s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.025654077529907227s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.2542307376861572s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010132789611816406s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.279151678085327s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.3392181396484375e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.26786255836486816s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.022126197814941406s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0011026859283447266s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.790855407714844e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-foreign took 2.831972599029541s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.03290200233459473s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.26134276390075684s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.893013000488281e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.382930040359497s
Availability | SPARQL endpoint availability check for fun took 0.03947710990905762s
Availability | VoID file availability check for fun took 0.0003571510314941406s
Completeness | Calculation of interlinking completeness for fun took 0.2542552947998047s
Reputation | Calculation of the PageRank for fun took 0.020558595657348633s
Interlinking | Calculation of Degree of Connection for fun took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for fun took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for fun took 7.414817810058594e-05s
Believability | Calculation of trust value for fun took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.3624093532562256s
Availability | SPARQL endpoint availability check for gdlc took 0.025874853134155273s
Availability | VoID file availability check for gdlc took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for gdlc took 0.23701119422912598s
Reputation | Calculation of the PageRank for gdlc took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for gdlc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for gdlc took 7.081031799316406e-05s
Believability | Calculation of trust value for gdlc took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.2686843872070312s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.04360342025756836s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.25229954719543457s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.0001366138458251953s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.3173959255218506s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.03608345985412598s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2683756351470947s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001380443572998047s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-ieee took 2.332481861114502s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.03555583953857422s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.2399883270263672s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00014019012451171875s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.3183860778808594s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.03863954544067383s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.24636459350585938s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02114391326904297s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.270408630371094e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.354696035385132s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.040549516677856445s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0003674030303955078s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.27226758003234863s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.700920104980469e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.3925106525421143s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.037149906158447266s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.24046111106872559s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.325176477432251s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.027534961700439453s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2767982482910156s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0001621246337890625s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.4041507244110107s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.037358999252319336s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.25774335861206055s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00015592575073242188s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.4004955291748047s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.041864633560180664s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2698991298675537s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.534027099609375e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.416170835494995s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.04116702079772949s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.25681567192077637s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.021616458892822266s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00017642974853515625s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.375148057937622s
Availability | SPARQL endpoint availability check for notube took 0.037156105041503906s
Availability | VoID file availability check for notube took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for notube took 0.25852155685424805s
Reputation | Calculation of the PageRank for notube took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for notube took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for notube took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for notube took 4.2438507080078125e-05s
Believability | Calculation of trust value for notube took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.3570382595062256s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.036794424057006836s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.2426137924194336s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.021367788314819336s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0009851455688476562s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00015306472778320312s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.3743138313293457s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.037828922271728516s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.25150227546691895s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00016689300537109375s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.373762369155884s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.267692565917969e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.2526977062225342s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020840883255004883s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.002086639404296875s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 3.647804260253906e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.794478416442871s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.025083303451538086s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.2517735958099365s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.021021127700805664s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.390975952148438e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-os took 2.3680431842803955s
Availability | SPARQL endpoint availability check for photos took 0.04071974754333496s
Availability | VoID file availability check for photos took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for photos took 0.2657480239868164s
Reputation | Calculation of the PageRank for photos took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for photos took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for photos took 0.0010204315185546875s
Interlinking | Calculation of Clustering coefficient for photos took 8.749961853027344e-05s
Believability | Calculation of trust value for photos took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.3646645545959473s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.027675867080688477s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.2637214660644531s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.021086454391479492s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00012230873107910156s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.3432655334472656s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.03531074523925781s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.252582311630249s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.02123284339904785s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019669532775878906s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.359269380569458s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.038181304931640625s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.25562477111816406s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020704269409179688s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00014448165893554688s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.3158061504364014s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.04078555107116699s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.26392173767089844s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020890474319458008s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.393692016601562e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.2980573177337646s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.04368758201599121s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.260164737701416s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00013113021850585938s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.356884717941284s
Availability | SPARQL endpoint availability check for roni took 0.03760027885437012s
Availability | VoID file availability check for roni took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for roni took 0.2580602169036865s
Reputation | Calculation of the PageRank for roni took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for roni took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for roni took 2.9802322387695312e-05s
Believability | Calculation of trust value for roni took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.372826337814331s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.033661603927612305s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0003254413604736328s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.25261878967285156s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.02111220359802246s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00022530555725097656s
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.3339149951934814s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.03808999061584473s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00037980079650878906s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.25820302963256836s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010943412780761719s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.372218608856201s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.0410914421081543s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.25535154342651367s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00010156631469726562s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.406467914581299s
Availability | SPARQL endpoint availability check for webconf took 0.036724090576171875s
Availability | VoID file availability check for webconf took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for webconf took 0.26790666580200195s
Reputation | Calculation of the PageRank for webconf took 0.020660400390625s
Interlinking | Calculation of Degree of Connection for webconf took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010395050048828125s
Believability | Calculation of trust value for webconf took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-webconf took 12.598933935165405s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.04079747200012207s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.25835466384887695s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 9.632110595703125e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.3495559692382812s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.0358271598815918s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2665224075317383s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020791292190551758s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00021004676818847656s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.3655784130096436s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.036875009536743164s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.2504146099090576s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.036064147949219e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.341294288635254s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.2438507080078125e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.258190393447876s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.020814895629882812s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 3.123283386230469e-05s
Believability | Calculation of trust value for RKB Explorer Data took 7.62939453125e-06s
INFO | --- Analysis for rkb_explorer_data took 2.835081100463867s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.410743713378906e-05s
Availability | VoID file availability check for The Rosetta Project took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.23421359062194824s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.0517578125e-05s
Believability | Calculation of trust value for The Rosetta Project took 7.867813110351562e-06s
INFO | --- Analysis for rosetta-project took 2.707801580429077s
Availability | SPARQL endpoint availability check for Rpm Find took 4.1961669921875e-05s
Availability | VoID file availability check for Rpm Find took 0.0003159046173095703s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.2388772964477539s
Reputation | Calculation of the PageRank for Rpm Find took 0.020685434341430664s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.0994415283203125e-05s
Believability | Calculation of trust value for Rpm Find took 8.106231689453125e-06s
INFO | --- Analysis for rpm_find took 2.6758108139038086s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.482269287109375e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0003962516784667969s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.24436163902282715s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0008218288421630859s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.914138793945312e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 8.106231689453125e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.490191698074341s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.4345855712890625e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0003509521484375s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2586236000061035s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.414817810058594e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 8.106231689453125e-06s
INFO | --- Analysis for rubentaelman took 2.6707255840301514s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.4345855712890625e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.26139020919799805s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020949840545654297s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.368492126464844e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 6.9141387939453125e-06s
INFO | --- Analysis for rubenverborgh took 3.0812106132507324s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.4942605495453s
Availability | VoID file availability check for Russian Universities Specialities took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.24446702003479004s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.021117448806762695s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.100799560546875e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 8.344650268554688e-06s
INFO | --- Analysis for russian-universities-specialities took 677.6859319210052s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.38690185546875e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.25049662590026855s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.62396240234375e-05s
Believability | Calculation of trust value for RuThes Cloud took 7.867813110351562e-06s
INFO | --- Analysis for ruthes took 4.143878698348999s
Availability | SPARQL endpoint availability check for RxNorm took 4.220008850097656e-05s
Availability | VoID file availability check for RxNorm took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for RxNorm took 0.25983262062072754s
Reputation | Calculation of the PageRank for RxNorm took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for RxNorm took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RxNorm took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.337860107421875e-05s
Believability | Calculation of trust value for RxNorm took 7.62939453125e-06s
INFO | --- Analysis for rxnorm took 4.2034196853637695s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 1.6801776885986328s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.2680399417877197s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 4.2438507080078125e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 8.58306884765625e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 5.347990989685059s
Availability | SPARQL endpoint availability check for SALDO took 4.2438507080078125e-05s
Availability | VoID file availability check for SALDO took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for SALDO took 0.24790501594543457s
Reputation | Calculation of the PageRank for SALDO took 0.02093338966369629s
Interlinking | Calculation of Degree of Connection for SALDO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.0517578125e-05s
Believability | Calculation of trust value for SALDO took 7.867813110351562e-06s
INFO | --- Analysis for saldo took 2.837341547012329s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.2298390865325928s
Availability | VoID file availability check for SALDO-RDF took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.24750113487243652s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for SALDO-RDF took 7.3909759521484375e-06s
INFO | --- Analysis for saldo-rdf took 5.703595399856567s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6386499404907227s
Availability | VoID file availability check for SALDOM-RDF took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2591421604156494s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.0013580322265625e-05s
INFO | --- Analysis for saldom-rdf took 4.648195028305054s
Availability | SPARQL endpoint availability check for sameAs.org took 4.5299530029296875e-05s
Availability | VoID file availability check for sameAs.org took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.25909948348999023s
Reputation | Calculation of the PageRank for sameAs.org took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 6.103515625e-05s
Believability | Calculation of trust value for sameAs.org took 6.9141387939453125e-06s
INFO | --- Analysis for sameas-org took 2.840134382247925s
Availability | SPARQL endpoint availability check for sandrart.net took 5.793571472167969e-05s
Availability | VoID file availability check for sandrart.net took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.2656724452972412s
Reputation | Calculation of the PageRank for sandrart.net took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for sandrart.net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.771087646484375e-05s
Believability | Calculation of trust value for sandrart.net took 7.867813110351562e-06s
INFO | --- Analysis for sandrart-net took 3.39443302154541s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.5336828231811523s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0012459754943847656s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.26004838943481445s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.0994415283203125e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 7.3909759521484375e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 6.102536201477051s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 262.29165029525757s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0008447170257568359s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.34742283821105957s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.021047115325927734s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.124641418457031e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 8.106231689453125e-06s
INFO | --- Analysis for santillana_guide_dataset took 668.0431921482086s
Availability | SPARQL endpoint availability check for schema.org took 4.3392181396484375e-05s
Availability | VoID file availability check for schema.org took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for schema.org took 0.7236635684967041s
Reputation | Calculation of the PageRank for schema.org took 0.02094435691833496s
Interlinking | Calculation of Degree of Connection for schema.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for schema.org took 5.5789947509765625e-05s
Believability | Calculation of trust value for schema.org took 9.059906005859375e-06s
INFO | --- Analysis for schema-org took 4.692704916000366s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 2.0031118392944336s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.6814188957214355s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.123283386230469e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 7.62939453125e-06s
INFO | --- Analysis for schemapedia took 6.0810980796813965s
Availability | SPARQL endpoint availability check for scholarlydata took 4.2438507080078125e-05s
Availability | VoID file availability check for scholarlydata took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.2686309814453125s
Reputation | Calculation of the PageRank for scholarlydata took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 2.9325485229492188e-05s
Believability | Calculation of trust value for scholarlydata took 1.3113021850585938e-05s
INFO | --- Analysis for scholarlydata took 3.75455379486084s
Availability | SPARQL endpoint availability check for Scholarometer took 4.363059997558594e-05s
Availability | VoID file availability check for Scholarometer took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.26932811737060547s
Reputation | Calculation of the PageRank for Scholarometer took 0.02070331573486328s
Interlinking | Calculation of Degree of Connection for Scholarometer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.678436279296875e-05s
Believability | Calculation of trust value for Scholarometer took 7.152557373046875e-06s
INFO | --- Analysis for scholarometer took 6.800300121307373s
Availability | SPARQL endpoint availability check for Science Commons took 4.3392181396484375e-05s
Availability | VoID file availability check for Science Commons took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Science Commons took 0.25647711753845215s
Reputation | Calculation of the PageRank for Science Commons took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for Science Commons took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Science Commons took 0.0009875297546386719s
Interlinking | Calculation of Clustering coefficient for Science Commons took 3.838539123535156e-05s
Believability | Calculation of trust value for Science Commons took 8.106231689453125e-06s
INFO | --- Analysis for science_commons took 2.792142629623413s
Availability | SPARQL endpoint availability check for ScienceWise took 4.3392181396484375e-05s
Availability | VoID file availability check for ScienceWise took 0.00032210350036621094s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2972066402435303s
Reputation | Calculation of the PageRank for ScienceWise took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for ScienceWise took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.0040740966796875e-05s
Believability | Calculation of trust value for ScienceWise took 8.106231689453125e-06s
INFO | --- Analysis for sciencewise took 2.8383374214172363s
Availability | SPARQL endpoint availability check for sears.com took 9.083747863769531e-05s
Availability | VoID file availability check for sears.com took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for sears.com took 0.24500155448913574s
Reputation | Calculation of the PageRank for sears.com took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for sears.com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for sears.com took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.651878356933594e-05s
Believability | Calculation of trust value for sears.com took 7.3909759521484375e-06s
INFO | --- Analysis for sears took 4.555984020233154s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.06596159934997559s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.26924729347229004s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.130073547363281e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.4836273193359375e-06s
INFO | --- Analysis for sec-rdfabout took 6.2420334815979s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.62085747718811s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0008070468902587891s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.26093602180480957s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020751237869262695s
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.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.893013000488281e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for secold took 167.52657914161682s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.267692565917969e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.2529909610748291s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.8848648071289062e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 8.106231689453125e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 3.7171008586883545s
Availability | SPARQL endpoint availability check for semanlink took 4.5299530029296875e-05s
Availability | VoID file availability check for semanlink took 0.0009543895721435547s
Completeness | Calculation of interlinking completeness for semanlink took 0.7758402824401855s
Reputation | Calculation of the PageRank for semanlink took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001552104949951172s
Believability | Calculation of trust value for semanlink took 7.62939453125e-06s
INFO | --- Analysis for semanlink took 183.65266919136047s
Availability | SPARQL endpoint availability check for Semantic Library took 4.76837158203125e-05s
Availability | VoID file availability check for Semantic Library took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.259502649307251s
Reputation | Calculation of the PageRank for Semantic Library took 0.02117300033569336s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 3.3855438232421875e-05s
Believability | Calculation of trust value for Semantic Library took 8.821487426757812e-06s
INFO | --- Analysis for semantic-library took 3.2807424068450928s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.3392181396484375e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.2682209014892578s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.123283386230469e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 7.62939453125e-06s
INFO | --- Analysis for semantic-profiling-network took 3.223046064376831s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.0883796215057373s
Availability | VoID file availability check for Semantic Universe Data took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.24087238311767578s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.8848648071289062e-05s
Believability | Calculation of trust value for Semantic Universe Data took 8.58306884765625e-06s
INFO | --- Analysis for semantic-universe took 2.400424003601074s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.087902784347534s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0007662773132324219s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.25176286697387695s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011801719665527344s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-web-dog-food took 82.70490837097168s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.410743713378906e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.2536628246307373s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.696846008300781e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 9.059906005859375e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.6379024982452393s
Availability | SPARQL endpoint availability check for semantic-web-journal took 5.14984130859375e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2509124279022217s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.0204925537109375s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.886222839355469e-05s
Believability | Calculation of trust value for semantic-web-journal took 8.106231689453125e-06s
INFO | --- Analysis for semantic-web-journal took 2.8146347999572754s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.744529724121094e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.2508420944213867s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007507801055908203s
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 6.198883056640625e-06s
INFO | --- Analysis for semantic-xbrl took 3.263256311416626s
Availability | SPARQL endpoint availability check for Semantic Bible took 5.14984130859375e-05s
Availability | VoID file availability check for Semantic Bible took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.2618577480316162s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 2.956390380859375e-05s
Believability | Calculation of trust value for Semantic Bible took 7.867813110351562e-06s
INFO | --- Analysis for semantic_bible took 2.7945408821105957s
Availability | SPARQL endpoint availability check for SemanticQuran took 6.947680234909058s
Availability | VoID file availability check for SemanticQuran took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.26061177253723145s
Reputation | Calculation of the PageRank for SemanticQuran took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.271766662597656e-05s
Believability | Calculation of trust value for SemanticQuran took 8.344650268554688e-06s
INFO | --- Analysis for semanticquran took 16.602654933929443s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.410743713378906e-05s
Availability | VoID file availability check for SemanticTweet took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.27558302879333496s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.507469177246094e-05s
Believability | Calculation of trust value for SemanticTweet took 7.152557373046875e-06s
INFO | --- Analysis for semantictweet took 2.455155849456787s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.38690185546875e-05s
Availability | VoID file availability check for semanticweb.org took 0.0014331340789794922s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.26404237747192383s
Reputation | Calculation of the PageRank for semanticweb.org took 0.021409988403320312s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.153915405273438e-05s
Believability | Calculation of trust value for semanticweb.org took 7.3909759521484375e-06s
INFO | --- Analysis for semanticweb-org took 22.642749071121216s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.08054828643798828s
Availability | VoID file availability check for Semantic CrunchBase took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.2636106014251709s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020834684371948242s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0008306503295898438s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 7.033348083496094e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 6.9141387939453125e-06s
INFO | --- Analysis for semsol-crunchbase took 2.398977279663086s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.4345855712890625e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.26609349250793457s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.021249055862426758s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.24249267578125e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 9.298324584960938e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.802975654602051s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.19958186149597168s
Availability | VoID file availability check for SentimentWortschatz took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2515408992767334s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 8.96453857421875e-05s
Believability | Calculation of trust value for SentimentWortschatz took 9.5367431640625e-06s
INFO | --- Analysis for sentiws took 3.2020678520202637s
Availability | SPARQL endpoint availability check for Serendipity took 7.692033529281616s
Availability | VoID file availability check for Serendipity took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Serendipity took 0.2660505771636963s
Reputation | Calculation of the PageRank for Serendipity took 0.021082401275634766s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Serendipity took 8.916854858398438e-05s
Believability | Calculation of trust value for Serendipity took 1.5735626220703125e-05s
INFO | --- Analysis for serendipity took 15.138286590576172s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.2799108028411865s
Availability | VoID file availability check for Shoah victims? names took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.23920130729675293s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.001104116439819336s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.9114227294921875e-05s
Believability | Calculation of trust value for Shoah victims? names took 8.58306884765625e-06s
INFO | --- Analysis for shoah-victims-names took 3.0946874618530273s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.315376281738281e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00032591819763183594s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.2633795738220215s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.409385681152344e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 8.344650268554688e-06s
INFO | --- Analysis for simile_data_collection took 2.797966241836548s
Availability | SPARQL endpoint availability check for SIMPLE took 4.482269287109375e-05s
Availability | VoID file availability check for SIMPLE took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.2548065185546875s
Reputation | Calculation of the PageRank for SIMPLE took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.1961669921875e-05s
Believability | Calculation of trust value for SIMPLE took 8.344650268554688e-06s
INFO | --- Analysis for simple took 7.620544195175171s
Availability | SPARQL endpoint availability check for SITC-V4 took 26.964578866958618s
Availability | VoID file availability check for SITC-V4 took 0.0008814334869384766s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.2587318420410156s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02109360694885254s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0009636878967285156s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.1484832763671875e-05s
Believability | Calculation of trust value for SITC-V4 took 4.76837158203125e-06s
INFO | --- Analysis for sitc-v4 took 125.51803040504456s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 5.4836273193359375e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.2640502452850342s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.600120544433594e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 7.62939453125e-06s
INFO | --- Analysis for slideshare2rdf took 2.2987778186798096s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.3392181396484375e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.25183820724487305s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 8.821487426757812e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.8002915382385254s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.458427429199219e-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.2624216079711914s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.0040740966796875e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 8.344650268554688e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.7506678104400635s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 4.922323942184448s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.2519223690032959s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.361701965332031e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 8.58306884765625e-06s
INFO | --- Analysis for smartlink took 14.38811707496643s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.38690185546875e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.25099873542785645s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.0517578125e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 7.152557373046875e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 2.7171542644500732s
Availability | SPARQL endpoint availability check for SocialLink took 4.363059997558594e-05s
Availability | VoID file availability check for SocialLink took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for SocialLink took 0.25836730003356934s
Reputation | Calculation of the PageRank for SocialLink took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for SocialLink took 3.0040740966796875e-05s
Believability | Calculation of trust value for SocialLink took 8.106231689453125e-06s
INFO | --- Analysis for sociallink took 2.827265501022339s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.20583009719848633s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0010619163513183594s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 16.702479124069214s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.44315338134765625s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.1894054412841797s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.546405553817749s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.35420656204223633s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.18533635139465332s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.341048002243042s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.1094508171081543s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.10698342323303223s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7489855289459229s
License | MR license check for Social Semantic Web Thesaurus took 0.12137293815612793s
License | HR license check for Social Semantic Web Thesaurus took 0.11823129653930664s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.10473227500915527s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.11634492874145508s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.1754152774810791s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.10597681999206543s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.11381316184997559s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.10568571090698242s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.488451957702637s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 3.528594970703125e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.12572908401489258s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.10541534423828125s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11351323127746582s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.0809023380279541s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.08007311820983887s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.18539953231811523s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.1934061050415039s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.5321524143218994s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 0.919257402420044s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.11827230453491211s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.10144543647766113s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09264183044433594s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4497203826904297s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012706756591796875s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.08847475051879883s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.3089637756347656s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.08762907981872559s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.1024091243743896s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.5264596939086914s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00015854835510253906s
Security | Sign check for Social Semantic Web Thesaurus took 0.09265017509460449s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 108.20159411430359s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.2568063735961914s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 0.00010180473327636719s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.6273205280303955s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 200.1243860721588s
Availability | SPARQL endpoint availability check for SORS took 4.363059997558594e-05s
Availability | VoID file availability check for SORS took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for SORS took 0.266369104385376s
Reputation | Calculation of the PageRank for SORS took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for SORS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SORS took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for SORS took 5.030632019042969e-05s
Believability | Calculation of trust value for SORS took 5.4836273193359375e-06s
INFO | --- Analysis for sors took 12.389779806137085s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.6253204345703125e-05s
Availability | VoID file availability check for Soudy České republiky took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.2679610252380371s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.020998239517211914s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.00084686279296875s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 3.7670135498046875e-05s
Believability | Calculation of trust value for Soudy České republiky took 7.152557373046875e-06s
INFO | --- Analysis for soudy--esk--republiky took 2.8057572841644287s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 5.626678466796875e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.27768850326538086s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0008029937744140625s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.274482727050781e-05s
Believability | Calculation of trust value for southampton-ac-uk took 7.152557373046875e-06s
INFO | --- Analysis for southampton-ac-uk took 3.551851272583008s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.1483097076416016s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.25814080238342285s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.0279159545898438e-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 10.345844030380249s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.3392181396484375e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.23874425888061523s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.655952453613281e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 8.106231689453125e-06s
INFO | --- Analysis for southampton-ecs-eprints took 5.414169073104858s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5249686241149902s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0003020763397216797s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 165.9483733177185s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.1684763431549072s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.1219425201416016s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.1159887313842773s
Versatility | Languages check for Spanish Linguistic Datasets took 45.72632956504822s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.080756425857544s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.15247702598571777s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.28707456588745117s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.2725834846496582s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.2849600315093994s
License | MR license check for Spanish Linguistic Datasets took 0.2924153804779053s
License | HR license check for Spanish Linguistic Datasets took 0.4091947078704834s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.2793118953704834s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.33777546882629395s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5542237758636475s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.2685885429382324s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.2890462875366211s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.2854940891265869s
Performance | Throughput check for Spanish Linguistic Datasets took 11.216667413711548s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 6.937980651855469e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.3029146194458008s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.27999114990234375s
Interlinking | skos check for Spanish Linguistic Datasets took 0.3059251308441162s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2167067527770996s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.28057050704956055s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5776476860046387s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5883708000183105s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 57.38595199584961s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.310455322265625s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.287569522857666s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.2712857723236084s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9116580486297607s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010500907897949219s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.640564203262329s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.28145265579223633s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.66947340965271s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.764776468276978s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 43.987534284591675s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.441044569015503s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.695880651473999s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.895340919494629s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.315157413482666s
Security | Sign check for Spanish Linguistic Datasets took 0.2836282253265381s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 10.916714906692505s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.47956204414367676s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 4.124641418457031e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 1.430511474609375e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 8.58306884765625e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 415.54919385910034s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.035437583923339844s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.25079870223999023s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 3.218650817871094e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.482269287109375e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 7.62939453125e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.36690092086792s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 4.172325134277344e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.24624180793762207s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 2.86102294921875e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 7.867813110351562e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 3.233809471130371s
Availability | SPARQL endpoint availability check for SPQR took 4.2438507080078125e-05s
Availability | VoID file availability check for SPQR took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for SPQR took 0.24244928359985352s
Reputation | Calculation of the PageRank for SPQR took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for SPQR took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SPQR took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.8848648071289062e-05s
Believability | Calculation of trust value for SPQR took 1.33514404296875e-05s
INFO | --- Analysis for spqr took 2.7722012996673584s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.2438507080078125e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.25162291526794434s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020504236221313477s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 7.62939453125e-06s
INFO | --- Analysis for srcmf took 2.3683197498321533s
Availability | SPARQL endpoint availability check for SSF took 6.508827209472656e-05s
Availability | VoID file availability check for SSF took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for SSF took 0.24780631065368652s
Reputation | Calculation of the PageRank for SSF took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for SSF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SSF took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for SSF took 2.956390380859375e-05s
Believability | Calculation of trust value for SSF took 6.67572021484375e-06s
INFO | --- Analysis for ssf-lexicon took 2.736793041229248s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.458427429199219e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.254288911819458s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.021533966064453125s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.647804260253906e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 7.62939453125e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.650355577468872s
Availability | SPARQL endpoint availability check for STAC took 4.7206878662109375e-05s
Availability | VoID file availability check for STAC took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for STAC took 0.24067401885986328s
Reputation | Calculation of the PageRank for STAC took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for STAC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for STAC took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for STAC took 3.0517578125e-05s
Believability | Calculation of trust value for STAC took 8.106231689453125e-06s
INFO | --- Analysis for stac took 2.7493011951446533s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 6.461143493652344e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.2559170722961426s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 2.9087066650390625e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 8.58306884765625e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.790100574493408s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.482269287109375e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.25093865394592285s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.02090930938720703s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0009694099426269531s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.647804260253906e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.106231689453125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 3.8571412563323975s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.112708568572998s
Availability | VoID file availability check for statistics.data.gov.uk took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.24631643295288086s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.021360397338867188s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0009810924530029297s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00011610984802246094s
Believability | Calculation of trust value for statistics.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for statistics-data-gov-uk took 3.6546695232391357s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.601478576660156e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.23353910446166992s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.020412445068359375s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.8133392333984375e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 8.58306884765625e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.786405086517334s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.27010059356689453s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010657310485839844s
Believability | Calculation of trust value for statusnet-1w6-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-1w6-org took 2.7253758907318115s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2624092102050781s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020298242568969727s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.6927719116210938e-05s
INFO | --- Analysis for statusnet-20100-org took 2.3634235858917236s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 5.984306335449219e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2431328296661377s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.343292236328125e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.5596210956573486s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.25038743019104004s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 7.915496826171875e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.296812057495117s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.24163436889648438s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.1552734375e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.3374195098876953s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.2621912956237793s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011563301086425781s
Believability | Calculation of trust value for statusnet-bka-li took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-bka-li took 2.6550214290618896s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.24800372123718262s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.719329833984375e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 7.62939453125e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.332338571548462s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.26445746421813965s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.76837158203125e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-ced117-net took 3.4952197074890137s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.2651379108428955s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.078315734863281e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.5517947673797607s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 6.628036499023438e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.2554614543914795s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.000110626220703125s
Believability | Calculation of trust value for statusnet-chromic-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.4658570289611816s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2537674903869629s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 0.0001010894775390625s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.56743049621582s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2566263675689697s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.277324914932251s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.25983452796936035s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.961822509765625e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 2.9917757511138916s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.25618863105773926s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02070450782775879s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010228157043457031s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.459851026535034s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.25495028495788574s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.151199340820312e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.326906681060791s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.25995469093322754s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.1021575927734375e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.1589744091033936s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.26525425910949707s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.02102041244506836s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-dtdns-net took 2.4918460845947266s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.25326108932495117s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.457069396972656e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.280442953109741s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.252913236618042s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.653236389160156e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.271094560623169s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 5.507469177246094e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.24424004554748535s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.274482727050781e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-fcac-com took 2.8267905712127686s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.25409698486328125s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.412101745605469e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 2.951355218887329s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 5.340576171875e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.26360297203063965s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00019240379333496094s
Believability | Calculation of trust value for statusnet-fragdev-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.036760091781616s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.26689648628234863s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.2950611114501953s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.25969433784484863s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00012755393981933594s
Believability | Calculation of trust value for statusnet-gegeweb-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.4406681060791016s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 0.0001068115234375s
Availability | VoID file availability check for statusnet-glou-org took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.26897120475769043s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.723403930664062e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-glou-org took 2.5527403354644775s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2513551712036133s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012063980102539062s
Believability | Calculation of trust value for statusnet-gomertronic-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.3216657638549805s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2674276828765869s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0009684562683105469s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00011873245239257812s
Believability | Calculation of trust value for statusnet-hackerposse-com took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.7038848400115967s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.25178003311157227s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.601478576660156e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-hii-co-il took 3.3940625190734863s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 5.340576171875e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0012335777282714844s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2524256706237793s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.059906005859375e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 5.513558864593506s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2532784938812256s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.476217031478882s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 5.745887756347656e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.23907256126403809s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020882129669189453s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.1961669921875e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.53768253326416s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.25533342361450195s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.025792360305786133s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.389617919921875e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 2.530703544616699s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.26352357864379883s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011897087097167969s
Believability | Calculation of trust value for statusnet-jonkman-ca took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.2636260986328125s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 5.626678466796875e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.25769829750061035s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.894371032714844e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.406977891921997s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2629220485687256s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.02142477035522461s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.340576171875e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.3326268196105957s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.26608991622924805s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.910064697265625e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.179990768432617s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 0.0006783008575439453s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.2505471706390381s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.02075362205505371s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.176399230957031e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.318711519241333s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 5.1021575927734375e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.24908900260925293s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02149057388305664s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.030632019042969e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.3613948822021484s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0010921955108642578s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2700614929199219s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.021468162536621094s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0008332729339599609s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.890296936035156e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.5311625003814697s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.25356078147888184s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.584426879882812e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.5531680583953857s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 7.724761962890625e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.2543981075286865s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.0001201629638671875s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.3412387371063232s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.25399303436279297s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.5371928215026855s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.8160552978515625e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.26152563095092773s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02077937126159668s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.00010037422180175781s
Believability | Calculation of trust value for statusnet-lydiastench-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.340611696243286s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.27052831649780273s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.02054619789123535s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.555152893066406e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.215379238128662s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.26415300369262695s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.0001595020294189453s
Believability | Calculation of trust value for statusnet-macno-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-macno-org took 2.292832612991333s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.26508641242980957s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02082085609436035s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.747245788574219e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.3565173149108887s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2602818012237549s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 9.179115295410156e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.05612254142761s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2520780563354492s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.0209963321685791s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00018596649169921875s
Believability | Calculation of trust value for statusnet-morphtown-de took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.412848711013794s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.2518641948699951s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.02088451385498047s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.00010037422180175781s
Believability | Calculation of trust value for statusnet-mrblog-nl took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.4758403301239014s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.25001955032348633s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.345642566680908s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 5.173683166503906e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.26038098335266113s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.5814249515533447s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2646360397338867s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00011348724365234375s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.3159730434417725s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.6253204345703125e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0003609657287597656s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2562897205352783s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020851850509643555s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.9280834197998047s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 6.127357482910156e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.24010515213012695s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020629167556762695s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.2969160079956055s
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.00045943260192871094s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.27081894874572754s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.344650268554688e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.4069812297821045s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.25624513626098633s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-panda-id-au took 3.315208911895752s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2610344886779785s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.655952453613281e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.3747198581695557s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.2544972896575928s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.021116256713867188s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 8.130073547363281e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.3793678283691406s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 5.340576171875e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.25277137756347656s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020357608795166016s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002357959747314453s
Believability | Calculation of trust value for statusnet-postblue-info took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.302912712097168s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.26482415199279785s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.556510925292969e-05s
Believability | Calculation of trust value for statusnet-progval-net took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-progval-net took 2.4343819618225098s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.25269317626953125s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020740985870361328s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00012254714965820312s
Believability | Calculation of trust value for statusnet-qdnx-org took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.6911473274230957s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2601139545440674s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.152322292327881s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.25523900985717773s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021767616271972656s
Believability | Calculation of trust value for statusnet-quitter-se took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.6391189098358154s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.2548794746398926s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010323524475097656s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.50308895111084s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.2551417350769043s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.936622619628906e-05s
Believability | Calculation of trust value for statusnet-recit-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-recit-org took 4.024658679962158s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 7.748603820800781e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.25548577308654785s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00015044212341308594s
Believability | Calculation of trust value for statusnet-russwurm-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-russwurm-org took 3.079461097717285s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0008635520935058594s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.2653625011444092s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.535385131835938e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-samnoble-org took 4.741318464279175s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.23590397834777832s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.20159912109375e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.427335739135742s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2626779079437256s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020981550216674805s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 2.9802322387695312e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.942054748535156e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.3404176235198975s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.25734806060791016s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.437301635742188e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.36877703666687s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.00041556358337402344s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.24442696571350098s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020902395248413086s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.271766662597656e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.055345058441162s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.2531285285949707s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020724058151245117s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021886825561523438s
Believability | Calculation of trust value for statusnet-skilledtests-com took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 2.63723087310791s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.26377248764038086s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010657310485839844s
Believability | Calculation of trust value for statusnet-somsants-net took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.3554646968841553s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.6253204345703125e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.24742770195007324s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0009109973907470703s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.000141143798828125s
Believability | Calculation of trust value for statusnet-soucy-cc took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.3331804275512695s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.935264587402344e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2503976821899414s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-spip-org took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-spip-org took 3.211196184158325s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.25682735443115234s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020804166793823242s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.3162388801574707s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 6.103515625e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.26294755935668945s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.025272607803344727s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0014696121215820312s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.0001575946807861328s
Believability | Calculation of trust value for statusnet-ssweeny-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.01338791847229s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.252044677734375s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00023245811462402344s
Believability | Calculation of trust value for statusnet-status-net took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-status-net took 3.3034794330596924s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 8.177757263183594e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.24417567253112793s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.3252665996551514s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.2546525001525879s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0008459091186523438s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.226799011230469e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.3269054889678955s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.26727294921875s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012183189392089844s
Believability | Calculation of trust value for statusnet-thelovebug-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.8474655151367188s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2597923278808594s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-thornton2-com took 5.119916200637817s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.25664496421813965s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00011301040649414062s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.638355255126953s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2589385509490967s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020825624465942383s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.719329833984375e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.251880168914795s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 8.058547973632812e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2560555934906006s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.747245788574219e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 12.585262537002563s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2583434581756592s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 4.3392181396484375e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.445112466812134s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.4345855712890625e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.26769161224365234s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for steak took 4.264830827713013s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 6.29425048828125e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.25331878662109375s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.364418029785156e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 7.62939453125e-06s
INFO | --- Analysis for stitch-rameau took 3.7977378368377686s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 7.605552673339844e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.2542698383331299s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.2901763916015625e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 9.5367431640625e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.8668529987335205s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.35919761657714844s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0006878376007080078s
Extra | Recovery of all triples for STW Thesaurus for Economics took 21.17487859725952s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.055708885192871s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6445345878601074s
Interoperability | New terms check for STW Thesaurus for Economics took 1.6079521179199219s
Versatility | Languages check for STW Thesaurus for Economics took 1.6066856384277344s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.4759373664855957s
Security | Check HTTPS for STW Thesaurus for Economics took 0.125746488571167s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2576167583465576s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.23941802978515625s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.2153308391571045s
License | MR license check for STW Thesaurus for Economics took 0.23712658882141113s
License | HR license check for STW Thesaurus for Economics took 2.2473597526550293s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.2598719596862793s
Understandability | Number of label check for STW Thesaurus for Economics took 0.5465631484985352s
Understandability | URI regex check for STW Thesaurus for Economics took 0.4837806224822998s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.24349093437194824s
Verifiability | Authors check for STW Thesaurus for Economics took 0.24457764625549316s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.2276148796081543s
Performance | Throughput check for STW Thesaurus for Economics took 10.535806655883789s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7191741466522217s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.24533820152282715s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.2372591495513916s
Interlinking | skos check for STW Thesaurus for Economics took 0.29442882537841797s
Interlinking | skos check for STW Thesaurus for Economics took 0.31009888648986816s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.23001861572265625s
Currency | Creation date check for STW Thesaurus for Economics took 0.4640953540802002s
Currency | Modification date check for STW Thesaurus for Economics took 0.4718289375305176s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.589040279388428s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 2.944659948348999s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2725222110748291s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2602052688598633s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.2542397975921631s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 4.86504340171814s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0869789123535156s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.407167434692383s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.25302791595458984s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.1370975971221924s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 2.2803196907043457s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.327298879623413s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.2486627101898193s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6920530796051025s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2606186866760254s
Security | Sign check for STW Thesaurus for Economics took 0.25828027725219727s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 1466.3229944705963s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.9349682331085205s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.023005962371826172s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.0001881122589111328s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 3.6903042793273926s
Believability | Calculation of trust value for STW Thesaurus for Economics took 8.821487426757812e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 1566.6123762130737s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.7297153472900391s
Availability | VoID file availability check for Sudoc bibliographic data took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.25753021240234375s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 5.0067901611328125e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 8.106231689453125e-06s
INFO | --- Analysis for sudocfr took 8.5328369140625s
Availability | SPARQL endpoint availability check for Surge Radio took 4.38690185546875e-05s
Availability | VoID file availability check for Surge Radio took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.2541818618774414s
Reputation | Calculation of the PageRank for Surge Radio took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.916854858398438e-05s
Believability | Calculation of trust value for Surge Radio took 8.344650268554688e-06s
INFO | --- Analysis for surge-radio took 4.173640012741089s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 5.793571472167969e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.4443812370300293s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2636256217956543s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020789384841918945s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.271766662597656e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 7.62939453125e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 5.850693702697754s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.0267934799194336s
Availability | VoID file availability check for SweFN-RDF took 0.0008559226989746094s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.2603023052215576s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for SweFN-RDF took 8.58306884765625e-06s
INFO | --- Analysis for swefn-rdf took 5.439745903015137s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.3392181396484375e-05s
Availability | VoID file availability check for SwetoDblp took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.25567126274108887s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020764589309692383s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.790855407714844e-05s
Believability | Calculation of trust value for SwetoDblp took 8.58306884765625e-06s
INFO | --- Analysis for sweto-dblp took 22.548949480056763s
Availability | SPARQL endpoint availability check for SymbolicData took 7.748603820800781e-05s
Availability | VoID file availability check for SymbolicData took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.2524898052215576s
Reputation | Calculation of the PageRank for SymbolicData took 0.02093052864074707s
Interlinking | Calculation of Degree of Connection for SymbolicData took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 4.1961669921875e-05s
Believability | Calculation of trust value for SymbolicData took 9.775161743164062e-06s
INFO | --- Analysis for symbolicdata took 3.218989849090576s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.4291086196899414s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0014498233795166016s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4781303405761719s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.8622763156890869s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 50.23705983161926s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 19.41206121444702s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.19883370399475098s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 13.860761404037476s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.11649131774902344s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.596550464630127s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.39325833320617676s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.1853780746459961s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.46221470832824707s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.032618284225464s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5760524272918701s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 38.17065644264221s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3597707748413086s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.2084822654724121s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.19221997261047363s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.18552041053771973s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.433945178985596s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 9.942054748535156e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.712127447128296s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.8163058757781982s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.6714098453521729s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5378119945526123s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.5389647483825684s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 2.991192102432251s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.7974658012390137s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 62.23265051841736s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.1933274269104004s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.25008726119995117s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0012195110321044922s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0014770030975341797s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.18207359313964844s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 44.896155834198s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.27976274490356445s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.5754525661468506s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.2942607402801514s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.684725522994995s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.0021283626556396484s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.4865591526031494s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.1963810920715332s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 11.352981328964233s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.3275918960571289s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02133655548095703s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 7.62939453125e-06s
INFO | --- Analysis for sztaki-lod took 476.200966835022s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.792213439941406e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.24944353103637695s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.030632019042969e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.2636184692382812e-05s
INFO | --- Analysis for t4gm-info took 6.036690950393677s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.363059997558594e-05s
Availability | VoID file availability check for tags2con delicious took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.24363446235656738s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02071070671081543s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.38690185546875e-05s
Believability | Calculation of trust value for tags2con delicious took 7.3909759521484375e-06s
INFO | --- Analysis for tags2con-delicious took 44.45416831970215s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 262.6362042427063s
Availability | VoID file availability check for Taiwan geographic names took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.6980793476104736s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020800113677978516s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.793571472167969e-05s
Believability | Calculation of trust value for Taiwan geographic names took 8.106231689453125e-06s
INFO | --- Analysis for taiwan-geographic-names took 669.0547480583191s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.458427429199219e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.00039124488830566406s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.2545504570007324s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.655952453613281e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 7.867813110351562e-06s
INFO | --- Analysis for talis-openlibrary took 5.304406642913818s
Availability | SPARQL endpoint availability check for TalkBank took 4.076957702636719e-05s
Availability | VoID file availability check for TalkBank took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for TalkBank took 0.6766173839569092s
Reputation | Calculation of the PageRank for TalkBank took 0.02077317237854004s
Interlinking | Calculation of Degree of Connection for TalkBank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TalkBank took 0.0008575916290283203s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.9802322387695312e-05s
Believability | Calculation of trust value for TalkBank took 7.62939453125e-06s
INFO | --- Analysis for talkbank took 3.2508955001831055s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.8931875228881836s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.25021886825561523s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00011944770812988281s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 8.106231689453125e-06s
INFO | --- Analysis for taxonconcept took 13.224824666976929s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 5.7220458984375e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.26279354095458984s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.916854858398438e-05s
Believability | Calculation of trust value for taxonconcept-assets took 6.9141387939453125e-06s
INFO | --- Analysis for taxonconcept-assets took 2.6509947776794434s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.506111145019531e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.26484179496765137s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02065277099609375s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 6.437301635742188e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 9.5367431640625e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.6407394409179688s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 1.8440215587615967s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.2553377151489258s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.020748138427734375s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.9591064453125e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 1.1920928955078125e-05s
INFO | --- Analysis for taxref-ld took 8.026566505432129s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.8659119606018s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.3840312957763672s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.021233797073364258s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.886222839355469e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 9.059906005859375e-06s
INFO | --- Analysis for tcga took 541.4198160171509s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.2140491008758545s
Availability | VoID file availability check for TCGA Roadmap took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.27033114433288574s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 9.608268737792969e-05s
Believability | Calculation of trust value for TCGA Roadmap took 8.821487426757812e-06s
INFO | --- Analysis for tcga-roadmap took 6.382236003875732s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.5654337406158447s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.812528133392334s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.021015167236328125s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00011444091796875s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 7.867813110351562e-06s
INFO | --- Analysis for tcmgenedit_dataset took 139.8859827518463s
Availability | SPARQL endpoint availability check for TDS took 4.363059997558594e-05s
Availability | VoID file availability check for TDS took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for TDS took 0.25212693214416504s
Reputation | Calculation of the PageRank for TDS took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for TDS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for TDS took 3.981590270996094e-05s
Believability | Calculation of trust value for TDS took 8.106231689453125e-06s
INFO | --- Analysis for tds took 5.370025396347046s
Availability | SPARQL endpoint availability check for TED Talks took 4.267692565917969e-05s
Availability | VoID file availability check for TED Talks took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for TED Talks took 0.24126744270324707s
Reputation | Calculation of the PageRank for TED Talks took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for TED Talks took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TED Talks took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for TED Talks took 2.956390380859375e-05s
Believability | Calculation of trust value for TED Talks took 1.3589859008789062e-05s
INFO | --- Analysis for ted-talks took 3.228365898132324s
Availability | SPARQL endpoint availability check for TEKORD took 4.363059997558594e-05s
Availability | VoID file availability check for TEKORD took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for TEKORD took 0.258044958114624s
Reputation | Calculation of the PageRank for TEKORD took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.7206878662109375e-05s
Believability | Calculation of trust value for TEKORD took 7.62939453125e-06s
INFO | --- Analysis for tekord took 5.49186897277832s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 2.452329158782959s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.27107977867126465s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020915985107421875s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00011324882507324219s
Believability | Calculation of trust value for Telegraphis Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for telegraphis took 8.218104600906372s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.410743713378906e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.23836493492126465s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.021117687225341797s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.390975952148438e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 8.106231689453125e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.76999807357788s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.2576596736907959s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 7.867813110351562e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.9369521141052246s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 5.1975250244140625e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.24504470825195312s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 3.910064697265625e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for terminesp took 2.821458339691162s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 5.1975250244140625e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.0003848075866699219s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.27547717094421387s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020800113677978516s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 3.409385681152344e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.152557373046875e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.8333234786987305s
Availability | SPARQL endpoint availability check for Teseo took 4.3392181396484375e-05s
Availability | VoID file availability check for Teseo took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Teseo took 0.2666592597961426s
Reputation | Calculation of the PageRank for Teseo took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Teseo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.123283386230469e-05s
Believability | Calculation of trust value for Teseo took 8.58306884765625e-06s
INFO | --- Analysis for teseo took 2.889299154281616s
Availability | SPARQL endpoint availability check for xxxxx took 260.56389689445496s
Availability | VoID file availability check for xxxxx took 0.0009894371032714844s
Completeness | Calculation of interlinking completeness for xxxxx took 0.748549222946167s
Reputation | Calculation of the PageRank for xxxxx took 0.02128314971923828s
Interlinking | Calculation of Degree of Connection for xxxxx took 6.794929504394531e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for xxxxx took 6.175041198730469e-05s
Believability | Calculation of trust value for xxxxx took 9.775161743164062e-06s
INFO | --- Analysis for testee took 795.6008822917938s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.2438507080078125e-05s
Availability | VoID file availability check for Texai Lexicon took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.693561315536499s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 2.9087066650390625e-05s
Believability | Calculation of trust value for Texai Lexicon took 7.867813110351562e-06s
INFO | --- Analysis for texai_lexicon took 3.74979829788208s
Availability | SPARQL endpoint availability check for The CIARD RING took 5.650520324707031e-05s
Availability | VoID file availability check for The CIARD RING took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.26364612579345703s
Reputation | Calculation of the PageRank for The CIARD RING took 0.020798683166503906s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.0994415283203125e-05s
Believability | Calculation of trust value for The CIARD RING took 9.298324584960938e-06s
INFO | --- Analysis for the-ciard-ring took 3.699514865875244s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.13428616523742676s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.23578739166259766s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.021091938018798828s
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.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.3855438232421875e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 9.5367431640625e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.4330058097839355s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.48151302337646484s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007388591766357422s
Extra | Recovery of all triples for The European Library Open Dataset took 1.1220409870147705s
Performance | Total latancy measurement for The European Library Open Dataset took 1.19046950340271s
Amount of data | Number of triples check for The European Library Open Dataset took 30.22243642807007s
Versatility | Languages check for The European Library Open Dataset took 0.25673627853393555s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.181254386901855s
Interpretability | RDF structures check for The European Library Open Dataset took 0.25621819496154785s
Versatility | Serialization formats check for The European Library Open Dataset took 0.25336527824401855s
Availability | RDF dump link check for The European Library Open Dataset took 0.23930740356445312s
License | MR license check for The European Library Open Dataset took 0.2400970458984375s
License | HR license check for The European Library Open Dataset took 0.2647562026977539s
Amount of data | Number of property check for The European Library Open Dataset took 0.2120664119720459s
Understandability | Number of label check for The European Library Open Dataset took 1.1917695999145508s
Understandability | URI regex check for The European Library Open Dataset took 0.48673081398010254s
Understandability | Vocabs check for The European Library Open Dataset took 0.2667722702026367s
Verifiability | Authors check for The European Library Open Dataset took 0.2201836109161377s
Verifiability | Publishers check for The European Library Open Dataset took 0.24375486373901367s
Performance | Throughput check for The European Library Open Dataset took 11.787815570831299s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.271766662597656e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.22655940055847168s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.32288646697998047s
Interlinking | skos check for The European Library Open Dataset took 0.3222031593322754s
Interlinking | skos check for The European Library Open Dataset took 0.3046591281890869s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.24182415008544922s
Currency | Creation date check for The European Library Open Dataset took 0.4622035026550293s
Currency | Modification date check for The European Library Open Dataset took 0.5053019523620605s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.47935342788696s
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.23272323608398438s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 0.8601505756378174s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.02896714210510254s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02881789207458496s
Consistency | Disjoint class check for The European Library Open Dataset took 0.23947858810424805s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.49817132949829s
Consistency | Misplaced classes for The European Library Open Dataset took 0.327495813369751s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.7539997100830078s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.3139574527740479s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.524596691131592s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.0328984260559082s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.24775457382202148s
Security | Sign check for The European Library Open Dataset took 0.31835079193115234s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 9.626840591430664s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.3473834991455078s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.318092346191406e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 2.1457672119140625e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 7.62939453125e-06s
INFO | --- Analysis for the-european-library-open-dataset took 397.4741463661194s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 0.2424297332763672s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.24126577377319336s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.021288394927978516s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00011658668518066406s
Believability | Calculation of trust value for The Eurostat Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for the-eurostat-linked-data took 3.550116539001465s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.410743713378906e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.27658653259277344s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.020804166793823242s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0008182525634765625s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.0994415283203125e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.239776611328125e-05s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 2.9080698490142822s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.4345855712890625e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0003674030303955078s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.2685694694519043s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02140355110168457s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0008740425109863281s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 9.059906005859375e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 8.58306884765625e-06s
INFO | --- Analysis for the-living-lod-cloud took 41.014790296554565s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 4.172325134277344e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.24051117897033691s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 3.337860107421875e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 8.344650268554688e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.2349631786346436s
Availability | SPARQL endpoint availability check for The View From took 0.08463835716247559s
Availability | VoID file availability check for The View From took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for The View From took 0.25571489334106445s
Reputation | Calculation of the PageRank for The View From took 0.021409988403320312s
Interlinking | Calculation of Degree of Connection for The View From took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for The View From took 0.0010819435119628906s
Interlinking | Calculation of Clustering coefficient for The View From took 9.870529174804688e-05s
Believability | Calculation of trust value for The View From took 8.821487426757812e-06s
INFO | --- Analysis for the-view-from took 2.3877947330474854s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.1484832763671875e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.24793553352355957s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0008165836334228516s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.0517578125e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 8.344650268554688e-06s
INFO | --- Analysis for thesaurus-bncf took 2.8300254344940186s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.363059997558594e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.251908540725708s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.075599670410156e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 7.3909759521484375e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.3425276279449463s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 5.5353734493255615s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.00036907196044921875s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.252840518951416s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.020605087280273438s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.367134094238281e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 8.344650268554688e-06s
INFO | --- Analysis for thesaurus-w took 11.404699087142944s
Availability | SPARQL endpoint availability check for theses.fr took 4.291534423828125e-05s
Availability | VoID file availability check for theses.fr took 0.0011591911315917969s
Completeness | Calculation of interlinking completeness for theses.fr took 0.2666332721710205s
Reputation | Calculation of the PageRank for theses.fr took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.078315734863281e-05s
Believability | Calculation of trust value for theses.fr took 8.821487426757812e-06s
INFO | --- Analysis for thesesfr took 3.7439889907836914s
Availability | SPARQL endpoint availability check for ThIST took 266.01959228515625s
Availability | VoID file availability check for ThIST took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for ThIST took 0.6973927021026611s
Reputation | Calculation of the PageRank for ThIST took 0.020914316177368164s
Interlinking | Calculation of Degree of Connection for ThIST took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.441375732421875e-05s
Believability | Calculation of trust value for ThIST took 9.059906005859375e-06s
INFO | --- Analysis for thist took 563.7782289981842s
Availability | SPARQL endpoint availability check for TIP took 39.01095390319824s
Availability | VoID file availability check for TIP took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for TIP took 0.7042169570922852s
Reputation | Calculation of the PageRank for TIP took 0.020803213119506836s
Interlinking | Calculation of Degree of Connection for TIP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010967254638671875s
Believability | Calculation of trust value for TIP took 1.0967254638671875e-05s
INFO | --- Analysis for tip took 80.51571774482727s
Availability | SPARQL endpoint availability check for Tourpedia took 4.4345855712890625e-05s
Availability | VoID file availability check for Tourpedia took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.687760591506958s
Reputation | Calculation of the PageRank for Tourpedia took 0.02124643325805664s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.218650817871094e-05s
Believability | Calculation of trust value for Tourpedia took 7.3909759521484375e-06s
INFO | --- Analysis for tourpedia took 3.684521198272705s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.9378137588500977s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.2638120651245117s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.410743713378906e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 7.867813110351562e-06s
INFO | --- Analysis for traditional-korean-medicine took 4.347964763641357s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.16826415061950684s
Availability | VoID file availability check for Traffic Scotland took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.25285911560058594s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.4332275390625e-05s
Believability | Calculation of trust value for Traffic Scotland took 6.4373016357421875e-06s
INFO | --- Analysis for traffic-scotland took 2.995675802230835s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.43522095680236816s
Availability | VoID file availability check for Transparency International Linked Data took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.2492353916168213s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010824203491210938s
Believability | Calculation of trust value for Transparency International Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for transparency-linked-data took 2.822263717651367s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.5935132503509521s
Availability | VoID file availability check for transport.data.gov.uk took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2589302062988281s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.02054429054260254s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.34600830078125e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 5.9604644775390625e-06s
INFO | --- Analysis for transport-data-gov-uk took 3.646993398666382s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 5.6743621826171875e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.2488420009613037s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.020861387252807617s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 3.361701965332031e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 6.9141387939453125e-06s
INFO | --- Analysis for transport-openuplabs took 2.754331588745117s
Availability | SPARQL endpoint availability check for Twarql took 10.436837434768677s
Availability | VoID file availability check for Twarql took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Twarql took 0.2552170753479004s
Reputation | Calculation of the PageRank for Twarql took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Twarql took 8.58306884765625e-05s
Believability | Calculation of trust value for Twarql took 7.867813110351562e-06s
INFO | --- Analysis for twarql took 12.79165005683899s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.458427429199219e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.24922871589660645s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.075599670410156e-05s
Believability | Calculation of trust value for TWC Data-gov took 5.0067901611328125e-06s
INFO | --- Analysis for twc-data-gov took 2.4586527347564697s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 4.506111145019531e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.00037932395935058594s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.24303054809570312s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0008087158203125s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 3.337860107421875e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 8.344650268554688e-06s
INFO | --- Analysis for twc-demos took 2.7656710147857666s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.13107991218566895s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.26128602027893066s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020816802978515625s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.170967102050781e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 5.4836273193359375e-06s
INFO | --- Analysis for twc-healthdata took 14.747049808502197s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.26410174369812s
Availability | VoID file availability check for Instance Hub (all) took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.2950284481048584s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 6.961822509765625e-05s
Believability | Calculation of trust value for Instance Hub (all) took 6.67572021484375e-06s
INFO | --- Analysis for twc-hub took 65.28534126281738s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.12322878837585449s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.3336451053619385s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00010824203491210938s
Believability | Calculation of trust value for IEEE VIS Source Data took 8.106231689453125e-06s
INFO | --- Analysis for twc-ieeevis took 100.56906032562256s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.4345855712890625e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.26087307929992676s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02305316925048828s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 0.0001010894775390625s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 6.67572021484375e-06s
INFO | --- Analysis for twc-logd took 2.4487202167510986s
Availability | SPARQL endpoint availability check for twc-opendap took 0.1267540454864502s
Availability | VoID file availability check for twc-opendap took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.36005258560180664s
Reputation | Calculation of the PageRank for twc-opendap took 0.020730972290039062s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 7.43865966796875e-05s
Believability | Calculation of trust value for twc-opendap took 8.58306884765625e-06s
INFO | --- Analysis for twc-opendap took 49.82191181182861s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 4.1961669921875e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.24909305572509766s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.020583152770996094s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 2.9802322387695312e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 8.106231689453125e-06s
INFO | --- Analysis for tweetskb took 2.7753336429595947s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 4.458427429199219e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.252105712890625s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 2.956390380859375e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 8.58306884765625e-06s
INFO | --- Analysis for twitter-lids took 2.7957818508148193s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.94415283203125s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.25212526321411133s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.267692565917969e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 7.62939453125e-06s
INFO | --- Analysis for ub-mannheim-linked-data took 4.569523811340332s
Availability | SPARQL endpoint availability check for Uberblic.org took 1.5142204761505127s
Availability | VoID file availability check for Uberblic.org took 0.0007910728454589844s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.25324440002441406s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010418891906738281s
Believability | Calculation of trust value for Uberblic.org took 8.58306884765625e-06s
INFO | --- Analysis for uberblic took 6.290481805801392s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.13210844993591309s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.2520713806152344s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00010013580322265625s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for uis-linked-data took 2.433525562286377s
Availability | SPARQL endpoint availability check for UK Legislation took 4.4345855712890625e-05s
Availability | VoID file availability check for UK Legislation took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.2536046504974365s
Reputation | Calculation of the PageRank for UK Legislation took 0.021039962768554688s
Interlinking | Calculation of Degree of Connection for UK Legislation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.726119995117188e-05s
Believability | Calculation of trust value for UK Legislation took 5.245208740234375e-06s
INFO | --- Analysis for uk-legislation-api took 3.243622064590454s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.458427429199219e-05s
Availability | VoID file availability check for UK Postcodes took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.25169873237609863s
Reputation | Calculation of the PageRank for UK Postcodes took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.7697296142578125e-05s
Believability | Calculation of trust value for UK Postcodes took 7.867813110351562e-06s
INFO | --- Analysis for uk-postcodes took 22.27347230911255s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 6.556510925292969e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.25158262252807617s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00012373924255371094s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 8.58306884765625e-06s
INFO | --- Analysis for umbel took 5.166105508804321s
Availability | SPARQL endpoint availability check for UMTHES took 4.458427429199219e-05s
Availability | VoID file availability check for UMTHES took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for UMTHES took 0.2638108730316162s
Reputation | Calculation of the PageRank for UMTHES took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for UMTHES took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UMTHES took 0.0009982585906982422s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.8160552978515625e-05s
Believability | Calculation of trust value for UMTHES took 5.4836273193359375e-06s
INFO | --- Analysis for umthes took 3.5747830867767334s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.4877643585205078s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.25554990768432617s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.021815776824951172s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0009479522705078125s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 4.5299530029296875e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 1.5020370483398438e-05s
INFO | --- Analysis for un-hazardous-numbers took 8.769265174865723s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.23883771896362305s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0010833740234375s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.790855407714844e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for unesco-thesaurus took 2.8653147220611572s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2626802921295166s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0010118484497070312s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.337860107421875e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for unescothes took 2.7858176231384277s
Availability | SPARQL endpoint availability check for UniProt took 1.7881808280944824s
Availability | VoID file availability check for UniProt took 0.0006694793701171875s
Extra | Recovery of all triples for UniProt took 15.576889753341675s
Performance | Total latancy measurement for UniProt took 3.7115793228149414s
Amount of data | Number of triples check for UniProt took 0.3752570152282715s
Versatility | Languages check for UniProt took 0.6596651077270508s
Interpretability | Number of blank nodes check for UniProt took 0.9174075126647949s
Security | Check HTTPS for UniProt took 1.5146667957305908s
Interpretability | RDF structures check for UniProt took 0.15500187873840332s
Versatility | Serialization formats check for UniProt took 0.1730813980102539s
Availability | RDF dump link check for UniProt took 0.17175960540771484s
License | MR license check for UniProt took 0.175567626953125s
License | HR license check for UniProt took 0.17214179039001465s
Amount of data | Number of property check for UniProt took 0.16879034042358398s
Understandability | Number of label check for UniProt took 0.18633317947387695s
Understandability | URI regex check for UniProt took 0.3063235282897949s
Understandability | Vocabs check for UniProt took 0.17355966567993164s
Verifiability | Authors check for UniProt took 0.1740281581878662s
Verifiability | Publishers check for UniProt took 0.16052532196044922s
Performance | Throughput check for UniProt took 18.5917649269104s
Amount of data | Check the number of entities for UniProt took 0.0001556873321533203s
Verifiability | Contribs. check for UniProt took 0.16019010543823242s
Interlinking | sameAs chians check for UniProt took 0.17105531692504883s
Interlinking | skos check for UniProt took 0.1768195629119873s
Interlinking | skos check for UniProt took 0.16098737716674805s
Timeliness | dataset update frequency check for UniProt took 0.17256426811218262s
Currency | Creation date check for UniProt took 0.3251001834869385s
Currency | Modification date check for UniProt took 0.32891035079956055s
Rep.Conc. | URIs length for UniProt took 125.86601614952087s
Interoperability | New vocabularies check for UniProt took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.1492936611175537s
Accuracy | Check Datatype consistency for UniProt took 7.380338907241821s
Consistency | Disjoint class check for UniProt took 0.15357446670532227s
Consistency | Check Ontology hijacking for UniProt took 0.16825270652770996s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.8404247760772705s
Conciseness | Check Extensional conciseness for UniProt took 2.665830612182617s
Security | Sign check for UniProt took 0.17657899856567383s
Availability | Check URIs Dereferenciability for UniProt took 4.168776273727417s
Completeness | Calculation of interlinking completeness for UniProt took 0.797614336013794s
Reputation | Calculation of the PageRank for UniProt took 0.02112555503845215s
Interlinking | Calculation of Degree of Connection for UniProt took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.270408630371094e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.1920928955078125e-06s
Believability | Calculation of trust value for UniProt took 9.059906005859375e-06s
INFO | --- Analysis for uniprot took 712.7577488422394s
Availability | SPARQL endpoint availability check for UniProt citations took 4.9114227294921875e-05s
Availability | VoID file availability check for UniProt citations took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.26476073265075684s
Reputation | Calculation of the PageRank for UniProt citations took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 3.981590270996094e-05s
Believability | Calculation of trust value for UniProt citations took 8.344650268554688e-06s
INFO | --- Analysis for uniprot-citations took 4.075880527496338s
Availability | SPARQL endpoint availability check for UniProt databases took 4.267692565917969e-05s
Availability | VoID file availability check for UniProt databases took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.26248693466186523s
Reputation | Calculation of the PageRank for UniProt databases took 0.02106308937072754s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0008649826049804688s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 3.314018249511719e-05s
Believability | Calculation of trust value for UniProt databases took 8.106231689453125e-06s
INFO | --- Analysis for uniprot-databases took 3.2924208641052246s
Availability | SPARQL endpoint availability check for uniprot-metadata took 4.649162292480469e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.7909488677978516s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 5.9604644775390625e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.3589859008789062e-05s
INFO | --- Analysis for uniprot-metadata took 4.123812913894653s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 5.745887756347656e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.2685120105743408s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 3.0279159545898438e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 8.344650268554688e-06s
INFO | --- Analysis for uniprot-taxonomy took 2.846524715423584s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.1484832763671875e-05s
Availability | VoID file availability check for UniProt UniParc took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.2500739097595215s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 2.86102294921875e-05s
Believability | Calculation of trust value for UniProt UniParc took 7.3909759521484375e-06s
INFO | --- Analysis for uniprot-uniparc took 2.817528486251831s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.76837158203125e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.2551419734954834s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 4.363059997558594e-05s
Believability | Calculation of trust value for UniProt UniPathway took 7.3909759521484375e-06s
INFO | --- Analysis for uniprot-unipathway took 2.8353464603424072s
Availability | SPARQL endpoint availability check for UniProtKB took 1.261150598526001s
Availability | VoID file availability check for UniProtKB took 0.0010106563568115234s
Extra | Recovery of all triples for UniProtKB took 17.164573907852173s
Performance | Total latancy measurement for UniProtKB took 3.1433074474334717s
Amount of data | Number of triples check for UniProtKB took 0.40941810607910156s
Interoperability | New terms check for UniProtKB took 1.827500343322754s
Versatility | Languages check for UniProtKB took 0.5455596446990967s
Interpretability | Number of blank nodes check for UniProtKB took 0.8655664920806885s
Interpretability | RDF structures check for UniProtKB took 0.3402419090270996s
Versatility | Serialization formats check for UniProtKB took 0.4329795837402344s
Availability | RDF dump link check for UniProtKB took 0.18076109886169434s
License | MR license check for UniProtKB took 0.15077686309814453s
License | HR license check for UniProtKB took 300.1467332839966s
Amount of data | Number of property check for UniProtKB took 328.95983719825745s
Understandability | Number of label check for UniProtKB took 355.40120005607605s
Understandability | URI regex check for UniProtKB took 20.166476249694824s
Understandability | Vocabs check for UniProtKB took 10.00759243965149s
Verifiability | Authors check for UniProtKB took 10.100056886672974s
Verifiability | Publishers check for UniProtKB took 117.02743196487427s
Performance | Throughput check for UniProtKB took 67.06213045120239s
Amount of data | Check the number of entities for UniProtKB took 0.00013256072998046875s
Verifiability | Contribs. check for UniProtKB took 329.9677646160126s
Interlinking | sameAs chians check for UniProtKB took 493.2601435184479s
Interlinking | skos check for UniProtKB took 380.7917284965515s
Interlinking | skos check for UniProtKB took 374.55617928504944s
Timeliness | dataset update frequency check for UniProtKB took 300.7507975101471s
Currency | Creation date check for UniProtKB took 381.5381495952606s
Currency | Modification date check for UniProtKB took 20.193504095077515s
Rep.Conc. | URIs length for UniProtKB took 25.501665830612183s
Interoperability | New vocabularies check for UniProtKB took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for UniProtKB took 10.090516090393066s
Accuracy | Check Datatype consistency for UniProtKB took 7.443286418914795s
Consistency | Disjoint class check for UniProtKB took 10.064568519592285s
Consistency | Check Ontology hijacking for UniProtKB took 9.99895191192627s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 11.331662893295288s
Conciseness | Check Extensional conciseness for UniProtKB took 2.693358898162842s
Security | Sign check for UniProtKB took 10.08833122253418s
Availability | Check URIs Dereferenciability for UniProtKB took 20.119643688201904s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.5874814987182617s
Reputation | Calculation of the PageRank for UniProtKB took 0.0210568904876709s
Interlinking | Calculation of Degree of Connection for UniProtKB took 7.891654968261719e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 7.152557373046875e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 9.5367431640625e-07s
Believability | Calculation of trust value for UniProtKB took 8.344650268554688e-06s
INFO | --- Analysis for uniprotkb took 4026.275007009506s
Availability | SPARQL endpoint availability check for UniProt UniRef took 4.267692565917969e-05s
Availability | VoID file availability check for UniProt UniRef took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.2546391487121582s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 3.0517578125e-05s
Believability | Calculation of trust value for UniProt UniRef took 7.867813110351562e-06s
INFO | --- Analysis for uniref took 3.6502623558044434s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 4.76837158203125e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.24615025520324707s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 3.170967102050781e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 9.298324584960938e-06s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 3.243121862411499s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 4.410743713378906e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.24461936950683594s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 3.218650817871094e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 7.867813110351562e-06s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 3.226708173751831s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.26537561416625977s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.272408246994019s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0008494853973388672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.259929895401001s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.022835493087768555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 5.04242730140686s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 4.76837158203125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.2522869110107422s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.119342565536499s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.25452232360839844s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.587294101715088s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.24254226684570312s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.143558263778687s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.26152849197387695s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.006592035293579s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.264725923538208s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 5.228243350982666s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 5.650520324707031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.2657909393310547s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.09559440612793s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.6253204345703125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.25013256072998047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.147798538208008s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.2602813243865967s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.025654077529907s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.25580549240112305s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 12.925636768341064s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 8.320808410644531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0007631778717041016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.24715375900268555s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.9591064453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 12.835274457931519s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2557191848754883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.020949840545654297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-danish took 5.679850101470947s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 5.650520324707031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.259552001953125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.159880876541138s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.2654106616973877s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 12.921214818954468s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.28772592544555664s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.049565315246582s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0008296966552734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.25896167755126953s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.03106141090393s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.2571256160736084s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.020992040634155273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 12.969112634658813s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.27059459686279297s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.184412717819214s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.2560296058654785s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 5.198153495788574s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2572784423828125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 12.950801610946655s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0008623600006103516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.25946497917175293s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 5.078315734863281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.181149959564209s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.2707021236419678s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.863739013671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.245941162109375s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.24637126922607422s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 4.893987417221069s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.27783918380737305s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 5.904772520065308s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.2454819679260254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.001127481460571289s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.839897155761719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 5.186593532562256s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.26167774200439453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 5.06951379776001s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.26059532165527344s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.093467950820923s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0007457733154296875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.26502108573913574s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.167239904403687s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.24302101135253906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.02149033546447754s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 5.188812255859375s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.261859655380249s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.117895603179932s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.27136874198913574s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-irish took 5.263784408569336s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.24580860137939453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.021021366119384766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0009021759033203125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.792213439941406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.061596632003784s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.25542473793029785s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.021149635314941406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.064220666885376s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 5.125999450683594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.24728918075561523s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 5.073454141616821s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 5.0067901611328125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.2503793239593506s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020987987518310547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 12.977041244506836s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.24326729774475098s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 5.131035566329956s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.25595617294311523s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 12.953826665878296s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 0.00011467933654785156s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.25090742111206055s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020879507064819336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.021560907363892s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.24761199951171875s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.157687425613403s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0008828639984130859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.26205873489379883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020912647247314453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 5.507469177246094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 12.967649698257446s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 5.6743621826171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.26326727867126465s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.08225393295288s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.25702571868896484s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-persian took 5.004097938537598s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.2576887607574463s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.102908611297607s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.35307741165161133s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.020501136779785156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 12.817121982574463s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.00080108642578125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.2638561725616455s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.792213439941406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 12.889312744140625s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.26009178161621094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.163242816925049s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.7206878662109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.25032544136047363s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.059565544128418s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 0.00013375282287597656s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.2531263828277588s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.02101874351501465s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.113918781280518s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.27115416526794434s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 5.1367857456207275s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 7.843971252441406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0009200572967529297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.25421714782714844s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02088308334350586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 4.887580871582031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.120671510696411s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0006964206695556641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.2387244701385498s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.020869731903076172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.016005277633667s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.24722862243652344s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.024247646331787s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.25311970710754395s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.02100348472595215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 12.824552536010742s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.2631833553314209s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.011133670806885s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.25292110443115234s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 12.925827264785767s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0010502338409423828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.2644670009613037s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 5.155337572097778s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.001233816146850586s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.2495284080505371s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 4.850439548492432s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.25925111770629883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.098589658737183s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.26079893112182617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.208431720733643s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.26058101654052734s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.100596904754639s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.26515698432922363s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.197316884994507s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.2621448040008545s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.115751028060913s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.2528989315032959s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.020398855209350586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.839897155761719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.123045206069946s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.3392181396484375e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.2581503391265869s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.020844697952270508s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.890296936035156e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 8.106231689453125e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.465077877044678s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 4.1484832763671875e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.25141191482543945s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.020917415618896484s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 3.147125244140625e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 6.198883056640625e-06s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 3.0979340076446533s
Availability | SPARQL endpoint availability check for University of Bristol took 4.4345855712890625e-05s
Availability | VoID file availability check for University of Bristol took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.26249003410339355s
Reputation | Calculation of the PageRank for University of Bristol took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.218650817871094e-05s
Believability | Calculation of trust value for University of Bristol took 6.4373016357421875e-06s
INFO | --- Analysis for university-of-bristol took 2.7823424339294434s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.315376281738281e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.26279306411743164s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.9114227294921875e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 7.152557373046875e-06s
INFO | --- Analysis for university-plymouth-reading-lists took 2.8056833744049072s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.38690185546875e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.26686668395996094s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020920515060424805s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 5.221366882324219e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 7.867813110351562e-06s
INFO | --- Analysis for university-sussex-reading-lists took 2.546643018722534s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 0.11574244499206543s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.2587895393371582s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.02079486846923828s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.343292236328125e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.0728836059570312e-05s
INFO | --- Analysis for unodc took 2.5882515907287598s
Availability | SPARQL endpoint availability check for URIBurner took 0.5588443279266357s
Availability | VoID file availability check for URIBurner took 0.0004622936248779297s
Extra | Recovery of all triples for URIBurner took 122.45866250991821s
Performance | Total latancy measurement for URIBurner took 1.2716636657714844s
Amount of data | Number of triples check for URIBurner took 3.035992383956909s
Interoperability | New terms check for URIBurner took 37.79232859611511s
Versatility | Languages check for URIBurner took 123.51315236091614s
Interpretability | Number of blank nodes check for URIBurner took 1.7227141857147217s
Security | Check HTTPS for URIBurner took 0.37270092964172363s
Interpretability | RDF structures check for URIBurner took 3.386101245880127s
Versatility | Serialization formats check for URIBurner took 6.214248180389404s
Availability | RDF dump link check for URIBurner took 45.37074041366577s
License | MR license check for URIBurner took 1.15995192527771s
License | HR license check for URIBurner took 122.03675484657288s
Amount of data | Number of property check for URIBurner took 0.4715232849121094s
Understandability | Number of label check for URIBurner took 3.150989055633545s
Understandability | URI regex check for URIBurner took 0.8552453517913818s
Understandability | Vocabs check for URIBurner took 0.33814287185668945s
Verifiability | Authors check for URIBurner took 0.42664361000061035s
Verifiability | Publishers check for URIBurner took 0.3805217742919922s
Performance | Throughput check for URIBurner took 11.590359449386597s
Amount of data | Check the number of entities for URIBurner took 9.274482727050781e-05s
Verifiability | Contribs. check for URIBurner took 0.36589860916137695s
Interlinking | sameAs chians check for URIBurner took 1.1486101150512695s
Interlinking | skos check for URIBurner took 0.6791610717773438s
Interlinking | skos check for URIBurner took 0.23427534103393555s
Timeliness | dataset update frequency check for URIBurner took 0.6404483318328857s
Currency | Creation date check for URIBurner took 2.4288527965545654s
Currency | Modification date check for URIBurner took 0.4922311305999756s
Rep.Conc. | URIs length for URIBurner took 114.37681031227112s
Interoperability | New vocabularies check for URIBurner took 25.487630605697632s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.3039102554321289s
Accuracy | Check Functional Property for URIBurner took 0.2973818778991699s
Accuracy | Check Inverse Functional Property for URIBurner took 0.25104427337646484s
Accuracy | Check Empty annotation labels for URIBurner took 56.016512632369995s
Accuracy | Check White space in annotation for URIBurner took 0.18713164329528809s
Consistency | Disjoint class check for URIBurner took 0.2742605209350586s
Consistency | Check Misplaced properties for URIBurner took 301.8775050640106s
Consistency | Misplaced classes for URIBurner took 57.527451038360596s
Consistency | Check Ontology hijacking for URIBurner took 58.57023572921753s
Consistency | Check Invalid usage of undefined properties for URIBurner took 58.502506494522095s
Conciseness | Check Extensional conciseness for URIBurner took 0.00017523765563964844s
Conciseness | Check Intensional conciseness for URIBurner took 111.45753169059753s
Security | Sign check for URIBurner took 0.6288025379180908s
Completeness | Calculation of interlinking completeness for URIBurner took 0.9088335037231445s
Reputation | Calculation of the PageRank for URIBurner took 0.02146148681640625s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0008227825164794922s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00010085105895996094s
Interoperability | Check the re-using of existing vocabs for URIBurner took 24.788630485534668s
Believability | Calculation of trust value for URIBurner took 8.58306884765625e-06s
INFO | --- Analysis for uriburner took 5865.0243282318115s
Availability | SPARQL endpoint availability check for US Political Violence took 7.557868957519531e-05s
Availability | VoID file availability check for US Political Violence took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.261829137802124s
Reputation | Calculation of the PageRank for US Political Violence took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for US Political Violence took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for US Political Violence took 0.0008132457733154297s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.0994415283203125e-05s
Believability | Calculation of trust value for US Political Violence took 9.5367431640625e-06s
INFO | --- Analysis for us-political-violence took 5.473508834838867s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.37285423278808594s
Availability | VoID file availability check for USAGE review corpus took 0.0011563301086425781s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.6822929382324219s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020833969116210938s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.147125244140625e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.0013580322265625e-05s
INFO | --- Analysis for usage-review-corpus took 4.29681658744812s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 6.124578475952148s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.00041794776916503906s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.2605247497558594s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.020868778228759766s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 8.416175842285156e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for utpl-lod took 11.227410316467285s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 4.458427429199219e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.259507417678833s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.021015405654907227s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 3.0040740966796875e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 8.106231689453125e-06s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 2.8468923568725586s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.338033676147461s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.00048828125s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.27453136444091797s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.845329284667969e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 9.059906005859375e-06s
INFO | --- Analysis for verrijktkoninkrijk took 14.656162977218628s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 4.506111145019531e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.24058961868286133s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.021077394485473633s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.0001728534698486328s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 7.3909759521484375e-06s
INFO | --- Analysis for viaf took 18.605420112609863s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 5.173683166503906e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.24311161041259766s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0008471012115478516s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 3.457069396972656e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 9.059906005859375e-06s
INFO | --- Analysis for vias-publicas-zaragoza took 2.687736749649048s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 5.412101745605469e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.2313215732574463s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 3.123283386230469e-05s
Believability | Calculation of trust value for vimeo.videoobject took 7.867813110351562e-06s
INFO | --- Analysis for vimeo_videoobject took 2.6794612407684326s
Availability | SPARQL endpoint availability check for VIVO took 5.7220458984375e-05s
Availability | VoID file availability check for VIVO took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for VIVO took 0.26027631759643555s
Reputation | Calculation of the PageRank for VIVO took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.914138793945312e-05s
Believability | Calculation of trust value for VIVO took 8.106231689453125e-06s
INFO | --- Analysis for vivo took 4.4644691944122314s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.458427429199219e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.24744224548339844s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.021045446395874023s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.273124694824219e-05s
Believability | Calculation of trust value for VIVO Cornell took 7.867813110351562e-06s
INFO | --- Analysis for vivo-cornell-university took 5.3410420417785645s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 4.267692565917969e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.2651681900024414s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 3.0994415283203125e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 9.059906005859375e-06s
INFO | --- Analysis for vivo-cu-boulder took 2.842562198638916s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.4345855712890625e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2680480480194092s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.082389831542969e-05s
Believability | Calculation of trust value for VIVO Indiana took 6.67572021484375e-06s
INFO | --- Analysis for vivo-indiana-university took 2.866379976272583s
Availability | SPARQL endpoint availability check for VIVO Ponce took 0.0001068115234375s
Availability | VoID file availability check for VIVO Ponce took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.2692747116088867s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.02125239372253418s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0010304450988769531s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 4.1484832763671875e-05s
Believability | Calculation of trust value for VIVO Ponce took 9.059906005859375e-06s
INFO | --- Analysis for vivo-ponce took 2.760610342025757s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 5.984306335449219e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0008237361907958984s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.2478020191192627s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.790855407714844e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 7.62939453125e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 2.7843117713928223s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.410743713378906e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.27447986602783203s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.020756959915161133s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.918212890625e-05s
Believability | Calculation of trust value for VIVO University of Florida took 7.152557373046875e-06s
INFO | --- Analysis for vivo-university-of-florida took 2.5453810691833496s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.4345855712890625e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.23751187324523926s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.0207674503326416s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.7670135498046875e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.7374346256256104s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.8160552978515625e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.26108860969543457s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.743171691894531e-05s
Believability | Calculation of trust value for VIVO WUSTL took 7.867813110351562e-06s
INFO | --- Analysis for vivo-wustl took 2.664649248123169s
Availability | SPARQL endpoint availability check for vivo2doi took 4.792213439941406e-05s
Availability | VoID file availability check for vivo2doi took 0.0007445812225341797s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.26654577255249023s
Reputation | Calculation of the PageRank for vivo2doi took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.482269287109375e-05s
Believability | Calculation of trust value for vivo2doi took 8.821487426757812e-06s
INFO | --- Analysis for vivo2doi took 23.36276340484619s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.506111145019531e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.2585172653198242s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 7.200241088867188e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 8.106231689453125e-06s
INFO | --- Analysis for vu-wordnet took 14.32663607597351s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.05718398094177246s
Availability | VoID file availability check for vulnerapedia took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.25113630294799805s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 7.176399230957031e-05s
Believability | Calculation of trust value for vulnerapedia took 7.62939453125e-06s
INFO | --- Analysis for vulnerapedia took 2.900317907333374s
Availability | SPARQL endpoint availability check for W3C took 5.9604644775390625e-05s
Availability | VoID file availability check for W3C took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for W3C took 0.23851776123046875s
Reputation | Calculation of the PageRank for W3C took 0.02073383331298828s
Interlinking | Calculation of Degree of Connection for W3C took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001430511474609375s
Believability | Calculation of trust value for W3C took 8.58306884765625e-06s
INFO | --- Analysis for w3c took 2.4758973121643066s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.267692565917969e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.24290871620178223s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.021086692810058594s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 3.147125244140625e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 7.867813110351562e-06s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.7802937030792236s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 5.364418029785156e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.24584579467773438s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.02092432975769043s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00011467933654785156s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.2874603271484375e-05s
INFO | --- Analysis for w3c-wordnet took 2.9817051887512207s
Availability | SPARQL endpoint availability check for WarSampo took 0.2977309226989746s
Availability | VoID file availability check for WarSampo took 0.0008213520050048828s
Extra | Recovery of all triples for WarSampo took 24.890490770339966s
Performance | Total latancy measurement for WarSampo took 0.8656153678894043s
Amount of data | Number of triples check for WarSampo took 20.485771656036377s
Interoperability | New terms check for WarSampo took 3.958266019821167s
Versatility | Languages check for WarSampo took 54.527530908584595s
Interpretability | Number of blank nodes check for WarSampo took 19.262751817703247s
Security | Check HTTPS for WarSampo took 0.42467379570007324s
Interpretability | RDF structures check for WarSampo took 0.18974733352661133s
Versatility | Serialization formats check for WarSampo took 0.20123577117919922s
Availability | RDF dump link check for WarSampo took 0.9914121627807617s
License | MR license check for WarSampo took 0.20961666107177734s
License | HR license check for WarSampo took 44.42152118682861s
Amount of data | Number of property check for WarSampo took 0.1951446533203125s
Understandability | Number of label check for WarSampo took 10.3647940158844s
Understandability | URI regex check for WarSampo took 0.36751604080200195s
Understandability | Vocabs check for WarSampo took 0.17422723770141602s
Verifiability | Authors check for WarSampo took 0.20850443840026855s
Verifiability | Publishers check for WarSampo took 0.19056105613708496s
Performance | Throughput check for WarSampo took 11.028716087341309s
Amount of data | Check the number of entities for WarSampo took 16.113558053970337s
Verifiability | Contribs. check for WarSampo took 0.2003173828125s
Interlinking | sameAs chians check for WarSampo took 0.21984577178955078s
Interlinking | skos check for WarSampo took 0.21628379821777344s
Interlinking | skos check for WarSampo took 0.1618654727935791s
Timeliness | dataset update frequency check for WarSampo took 0.17609405517578125s
Currency | Creation date check for WarSampo took 0.36746716499328613s
Currency | Modification date check for WarSampo took 0.3782031536102295s
Rep.Conc. | URIs length for WarSampo took 50.7604455947876s
Interoperability | New vocabularies check for WarSampo took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.1863386631011963s
Accuracy | Check Functional Property for WarSampo took 0.19777679443359375s
Accuracy | Check Inverse Functional Property for WarSampo took 0.17171430587768555s
Accuracy | Check Empty annotation labels for WarSampo took 18.245624780654907s
Accuracy | Check White space in annotation for WarSampo took 2.2839436531066895s
Accuracy | Check Datatype consistency for WarSampo took 5.438169240951538s
Consistency | Disjoint class check for WarSampo took 0.19936704635620117s
Consistency | Check Misplaced properties for WarSampo took 20.46283268928528s
Consistency | Check Ontology hijacking for WarSampo took 19.762364625930786s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.455608606338501s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.7151544094085693s
Conciseness | Check Extensional conciseness for WarSampo took 2.8955318927764893s
Conciseness | Check Intensional conciseness for WarSampo took 0.27523207664489746s
Security | Sign check for WarSampo took 0.16049671173095703s
Availability | Check URIs Dereferenciability for WarSampo took 2.641632080078125s
Completeness | Calculation of interlinking completeness for WarSampo took 0.4611051082611084s
Reputation | Calculation of the PageRank for WarSampo took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for WarSampo took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WarSampo took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.6689300537109375e-06s
Believability | Calculation of trust value for WarSampo took 8.821487426757812e-06s
INFO | --- Analysis for warsampo took 919.3438682556152s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.38130760192871094s
Availability | VoID file availability check for WebIsALOD took 0.0004584789276123047s
Extra | Recovery of all triples for WebIsALOD took 1.7306571006774902s
Performance | Total latancy measurement for WebIsALOD took 1.0077266693115234s
Amount of data | Number of triples check for WebIsALOD took 28.485458374023438s
Interoperability | New terms check for WebIsALOD took 19.837196588516235s
Versatility | Languages check for WebIsALOD took 61.748544692993164s
Interpretability | Number of blank nodes check for WebIsALOD took 0.22892236709594727s
Security | Check HTTPS for WebIsALOD took 0.11049437522888184s
Interpretability | RDF structures check for WebIsALOD took 0.24880123138427734s
Versatility | Serialization formats check for WebIsALOD took 0.2382044792175293s
Availability | RDF dump link check for WebIsALOD took 1.632028341293335s
License | MR license check for WebIsALOD took 0.2785625457763672s
License | HR license check for WebIsALOD took 23.642200469970703s
Amount of data | Number of property check for WebIsALOD took 0.25573086738586426s
Understandability | Number of label check for WebIsALOD took 0.6294004917144775s
Understandability | URI regex check for WebIsALOD took 0.5260007381439209s
Understandability | Vocabs check for WebIsALOD took 0.2523064613342285s
Verifiability | Authors check for WebIsALOD took 0.2289588451385498s
Verifiability | Publishers check for WebIsALOD took 0.24195575714111328s
Performance | Throughput check for WebIsALOD took 11.02536416053772s
Amount of data | Check the number of entities for WebIsALOD took 7.200241088867188e-05s
Verifiability | Contribs. check for WebIsALOD took 0.25507473945617676s
Interlinking | sameAs chians check for WebIsALOD took 0.3357090950012207s
Interlinking | skos check for WebIsALOD took 0.272580623626709s
Interlinking | skos check for WebIsALOD took 0.1960768699645996s
Timeliness | dataset update frequency check for WebIsALOD took 0.24651193618774414s
Currency | Creation date check for WebIsALOD took 0.48235297203063965s
Currency | Modification date check for WebIsALOD took 0.4699971675872803s
Rep.Conc. | URIs length for WebIsALOD took 81.61050510406494s
Interoperability | New vocabularies check for WebIsALOD took 3.409724712371826s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.25083136558532715s
Accuracy | Check Functional Property for WebIsALOD took 0.26494884490966797s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.23564481735229492s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.5242526531219482s
Accuracy | Check White space in annotation for WebIsALOD took 0.03038167953491211s
Accuracy | Check Datatype consistency for WebIsALOD took 0.030490398406982422s
Consistency | Disjoint class check for WebIsALOD took 0.2531883716583252s
Consistency | Check Misplaced properties for WebIsALOD took 61.00027942657471s
Consistency | Misplaced classes for WebIsALOD took 0.35341763496398926s
Consistency | Check Ontology hijacking for WebIsALOD took 2.3161122798919678s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.861018419265747s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 63.372886180877686s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.03492236137390137s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.28238630294799805s
Security | Sign check for WebIsALOD took 0.26174187660217285s
Availability | Check URIs Dereferenciability for WebIsALOD took 11.52637529373169s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.28736019134521484s
Reputation | Calculation of the PageRank for WebIsALOD took 0.02236461639404297s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 8.440017700195312e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 9.393692016601562e-05s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 2.980670690536499s
Believability | Calculation of trust value for WebIsALOD took 1.3828277587890625e-05s
INFO | --- Analysis for webisalod took 560.4510428905487s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 5.8650970458984375e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0007545948028564453s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.268230676651001s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.02106332778930664s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 4.124641418457031e-05s
Believability | Calculation of trust value for webnmasunotraveler took 8.344650268554688e-06s
INFO | --- Analysis for webnmasunotraveler took 10.377696990966797s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 4.38690185546875e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.25461745262145996s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.534027099609375e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.0013580322265625e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 2.83966326713562s
Availability | SPARQL endpoint availability check for WikiPathways took 5.078315734863281e-05s
Availability | VoID file availability check for WikiPathways took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.25607943534851074s
Reputation | Calculation of the PageRank for WikiPathways took 0.021772146224975586s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.001123189926147461s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 4.029273986816406e-05s
Believability | Calculation of trust value for WikiPathways took 9.775161743164062e-06s
INFO | --- Analysis for wikipathways took 3.299487590789795s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 4.363059997558594e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.2534353733062744s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.021098613739013672s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 3.123283386230469e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 1.0013580322265625e-05s
INFO | --- Analysis for wikiword_thesaurus took 2.8831098079681396s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.23350906372070312s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.25197887420654297s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.020785093307495117s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0009872913360595703s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 0.00010347366333007812s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.6927719116210938e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 3.1109118461608887s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 7.510185241699219e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.256009578704834s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.021295785903930664s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0009024143218994141s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 3.600120544433594e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 1.0967254638671875e-05s
INFO | --- Analysis for wings-workflow-provenance-dataset took 2.8287887573242188s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.14171314239501953s
Availability | VoID file availability check for World Loanword Database took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.23968052864074707s
Reputation | Calculation of the PageRank for World Loanword Database took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.367134094238281e-05s
Believability | Calculation of trust value for World Loanword Database took 8.821487426757812e-06s
INFO | --- Analysis for wold took 2.4317026138305664s
Availability | SPARQL endpoint availability check for Wordnet took 4.363059997558594e-05s
Availability | VoID file availability check for Wordnet took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Wordnet took 0.26193737983703613s
Reputation | Calculation of the PageRank for Wordnet took 0.021375179290771484s
Interlinking | Calculation of Degree of Connection for Wordnet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wordnet took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Wordnet took 4.38690185546875e-05s
Believability | Calculation of trust value for Wordnet took 9.059906005859375e-06s
INFO | --- Analysis for wordnet took 2.8476507663726807s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.315376281738281e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.2348158359527588s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.322166442871094e-05s
Believability | Calculation of trust value for WordNet-RDF took 9.5367431640625e-06s
INFO | --- Analysis for wordnet-rdf took 2.362705945968628s
Availability | SPARQL endpoint availability check for wordpress took 4.38690185546875e-05s
Availability | VoID file availability check for wordpress took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for wordpress took 0.24535012245178223s
Reputation | Calculation of the PageRank for wordpress took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for wordpress took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for wordpress took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.630752563476562e-05s
Believability | Calculation of trust value for wordpress took 9.5367431640625e-06s
INFO | --- Analysis for wordpress took 2.718005418777466s
Availability | SPARQL endpoint availability check for wordpress.post took 4.363059997558594e-05s
Availability | VoID file availability check for wordpress.post took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.26444458961486816s
Reputation | Calculation of the PageRank for wordpress.post took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for wordpress.post took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for wordpress.post took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 2.9802322387695312e-05s
Believability | Calculation of trust value for wordpress.post took 7.62939453125e-06s
INFO | --- Analysis for wordpress_post took 2.765774965286255s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 1.034060001373291s
Availability | VoID file availability check for World Bank Linked Data took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.25054121017456055s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00013256072998046875s
Believability | Calculation of trust value for World Bank Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for world-bank-linked-data took 3.35693097114563s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.8380930423736572s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.25629448890686035s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02077651023864746s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.511543273925781e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 8.106231689453125e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 5.228085517883301s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 7.963180541992188e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.25111985206604004s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.440017700195312e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 5.0067901611328125e-06s
INFO | --- Analysis for world-wide-web-foundation took 5.492992877960205s
Availability | SPARQL endpoint availability check for WikiPathways took 7.295608520507812e-05s
Availability | VoID file availability check for WikiPathways took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2479248046875s
Reputation | Calculation of the PageRank for WikiPathways took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.123283386230469e-05s
Believability | Calculation of trust value for WikiPathways took 7.62939453125e-06s
INFO | --- Analysis for wp took 2.8215606212615967s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 4.267692565917969e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.2501382827758789s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 3.147125244140625e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 8.106231689453125e-06s
INFO | --- Analysis for wunderground_weatherreport took 2.7657418251037598s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.19420981407165527s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005159378051757812s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 3.3560619354248047s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8677165508270264s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.24130702018737793s
Interoperability | New terms check for World War 1 as Linked Open Data took 2.7188358306884766s
Versatility | Languages check for World War 1 as Linked Open Data took 0.6210932731628418s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.24562859535217285s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.25052404403686523s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.7414352893829346s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.2515852451324463s
Availability | RDF dump link check for World War 1 as Linked Open Data took 5.252265930175781s
License | MR license check for World War 1 as Linked Open Data took 0.20153284072875977s
License | HR license check for World War 1 as Linked Open Data took 1.6102511882781982s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.18795132637023926s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.3839075565338135s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.3604750633239746s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.2418532371520996s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.22145390510559082s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.19195151329040527s
Performance | Throughput check for World War 1 as Linked Open Data took 11.155901670455933s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07269072532653809s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.1912236213684082s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.22530865669250488s
Interlinking | skos check for World War 1 as Linked Open Data took 0.20617341995239258s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1626279354095459s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.16506457328796387s
Currency | Creation date check for World War 1 as Linked Open Data took 0.3914463520050049s
Currency | Modification date check for World War 1 as Linked Open Data took 0.1998124122619629s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.0662853717803955s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 5.8933796882629395s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.19806671142578125s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.19766998291015625s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.16425061225891113s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.1499555110931396s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.05352282524108887s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.3157055377960205s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.19797921180725098s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6169195175170898s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.108358383178711s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.294245958328247s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5523324012756348s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.18956518173217773s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.9514038562774658s
Security | Sign check for World War 1 as Linked Open Data took 0.22356224060058594s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1617.5160348415375s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 1.3805046081542969s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.023340463638305664s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 9.1552734375e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 9.894371032714844e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 6.477255821228027s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 9.775161743164062e-06s
INFO | --- Analysis for ww1lod took 1705.0525867938995s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 4.172325134277344e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.25482821464538574s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 3.0517578125e-05s
Believability | Calculation of trust value for XlendiAmphorae took 7.62939453125e-06s
INFO | --- Analysis for xlendiamphorae took 3.729191780090332s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.29430484771728516s
Availability | VoID file availability check for xLiD-Lexica took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.26737046241760254s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.009506225585938e-05s
Believability | Calculation of trust value for xLiD-Lexica took 9.059906005859375e-06s
INFO | --- Analysis for xlid-lexica took 4.192943572998047s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.4345855712890625e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.24543309211730957s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.933906555175781e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 8.106231689453125e-06s
INFO | --- Analysis for xwn took 2.5010504722595215s
Availability | SPARQL endpoint availability check for YAGO took 4.410743713378906e-05s
Availability | VoID file availability check for YAGO took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for YAGO took 0.2616236209869385s
Reputation | Calculation of the PageRank for YAGO took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for YAGO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for YAGO took 0.0008220672607421875s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.0001385211944580078s
Believability | Calculation of trust value for YAGO took 8.106231689453125e-06s
INFO | --- Analysis for yago took 4.691051721572876s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 1.4144952297210693s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.26572656631469727s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.987022399902344e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.7642974853515625e-05s
INFO | --- Analysis for yahoo_geoplanet took 15.250441312789917s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.13402152061462402s
Availability | VoID file availability check for Yale Senselab took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.25566530227661133s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.075599670410156e-05s
Believability | Calculation of trust value for Yale Senselab took 8.344650268554688e-06s
INFO | --- Analysis for yale_senselab took 11.208881378173828s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.9072268009185791s
Availability | VoID file availability check for Yovisto - academic video search took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.258573055267334s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.985664367675781e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 5.245208740234375e-06s
INFO | --- Analysis for yovisto took 25.8603994846344s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 4.315376281738281e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.26092004776000977s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.3855438232421875e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 7.62939453125e-06s
INFO | --- Analysis for ysa took 4.405652761459351s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.410743713378906e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.2591986656188965s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.020635604858398438s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.218650817871094e-05s
Believability | Calculation of trust value for yso-fi-allars took 7.62939453125e-06s
INFO | --- Analysis for yso-fi-allars took 3.4543490409851074s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.363059997558594e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0007944107055664062s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.24445271492004395s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.020969390869140625s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0010590553283691406s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 4.00543212890625e-05s
Believability | Calculation of trust value for yso-fi-ysa took 8.58306884765625e-06s
INFO | --- Analysis for yso-fi-ysa took 3.1125452518463135s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.291534423828125e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.24175357818603516s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.504753112792969e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 5.7220458984375e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 6.793992757797241s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 4.363059997558594e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.24657893180847168s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.2901763916015625e-05s
Believability | Calculation of trust value for zaragoza_turruta took 7.3909759521484375e-06s
INFO | --- Analysis for zaragoza_turruta took 2.538109064102173s
Availability | SPARQL endpoint availability check for ZBW Labs took 5.078315734863281e-05s
Availability | VoID file availability check for ZBW Labs took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.24208974838256836s
Reputation | Calculation of the PageRank for ZBW Labs took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 7.104873657226562e-05s
Believability | Calculation of trust value for ZBW Labs took 8.58306884765625e-06s
INFO | --- Analysis for zbw-labs took 3.172790765762329s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.15877962112426758s
Availability | VoID file availability check for 20th Century Press Archives took 0.0005998611450195312s
Extra | Recovery of all triples for 20th Century Press Archives took 46.13074541091919s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7049140930175781s
Amount of data | Number of triples check for 20th Century Press Archives took 1.7347958087921143s
Interoperability | New terms check for 20th Century Press Archives took 1.673710823059082s
Versatility | Languages check for 20th Century Press Archives took 5.267779350280762s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.8639953136444092s
Interpretability | RDF structures check for 20th Century Press Archives took 0.14364314079284668s
Versatility | Serialization formats check for 20th Century Press Archives took 0.17499041557312012s
Availability | RDF dump link check for 20th Century Press Archives took 0.14133405685424805s
License | MR license check for 20th Century Press Archives took 0.1532115936279297s
License | HR license check for 20th Century Press Archives took 4.96318793296814s
Amount of data | Number of property check for 20th Century Press Archives took 0.15606427192687988s
Understandability | Number of label check for 20th Century Press Archives took 0.4745335578918457s
Understandability | URI regex check for 20th Century Press Archives took 0.2846035957336426s
Understandability | Vocabs check for 20th Century Press Archives took 0.12515878677368164s
Verifiability | Authors check for 20th Century Press Archives took 0.14326167106628418s
Verifiability | Publishers check for 20th Century Press Archives took 0.14104795455932617s
Performance | Throughput check for 20th Century Press Archives took 10.84999680519104s
Amount of data | Check the number of entities for 20th Century Press Archives took 0.00012922286987304688s
Verifiability | Contribs. check for 20th Century Press Archives took 0.12915611267089844s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.12960529327392578s
Interlinking | skos check for 20th Century Press Archives took 0.174940824508667s
Interlinking | skos check for 20th Century Press Archives took 0.1637859344482422s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.14149093627929688s
Currency | Creation date check for 20th Century Press Archives took 0.2799947261810303s
Currency | Modification date check for 20th Century Press Archives took 0.31139087677001953s
Rep.Conc. | URIs length for 20th Century Press Archives took 14.469210624694824s
Interoperability | New vocabularies check for 20th Century Press Archives took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.16127467155456543s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.1613931655883789s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.1298689842224121s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 4.443147897720337s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8977658748626709s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.086806058883667s
Consistency | Disjoint class check for 20th Century Press Archives took 0.1566472053527832s
Consistency | Check Misplaced properties for 20th Century Press Archives took 1.9509000778198242s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.4582736492156982s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.683112382888794s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.1847381591796875s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.765484094619751s
Security | Sign check for 20th Century Press Archives took 0.15077733993530273s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 992.5629482269287s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.9160335063934326s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.02247762680053711s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 6.794929504394531e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00011992454528808594s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.6689300537109375e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 8.58306884765625e-06s
INFO | --- Analysis for zbw-pressemappe20 took 1134.0309610366821s
Availability | SPARQL endpoint availability check for zhishi.lemon took 5.602836608886719e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.25747156143188477s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.021129369735717773s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0011463165283203125s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 5.984306335449219e-05s
Believability | Calculation of trust value for zhishi.lemon took 8.106231689453125e-06s
INFO | --- Analysis for zhishi-lemon took 24.98203206062317s
Availability | SPARQL endpoint availability check for Zhishi.me took 2.9458370208740234s
Availability | VoID file availability check for Zhishi.me took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.26050782203674316s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0008511543273925781s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.510185241699219e-05s
Believability | Calculation of trust value for Zhishi.me took 7.3909759521484375e-06s
INFO | --- Analysis for zhishi-me took 6.749212741851807s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.315376281738281e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.25173258781433105s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.020349979400634766s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 5.91278076171875e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 7.867813110351562e-06s
INFO | --- Analysis for zitgist-musicbrainz took 2.7361316680908203s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.3105015754699707s
Availability | VoID file availability check for performing-arts.ch took 0.00025081634521484375s
Extra | Recovery of all triples for performing-arts.ch took 15.728161811828613s
Performance | Total latancy measurement for performing-arts.ch took 0.7617855072021484s
Amount of data | Number of triples check for performing-arts.ch took 34.808950901031494s
Interoperability | New terms check for performing-arts.ch took 1.499525785446167s
Versatility | Languages check for performing-arts.ch took 60.12122941017151s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.120206117630005s
Interpretability | RDF structures check for performing-arts.ch took 0.21213531494140625s
Versatility | Serialization formats check for performing-arts.ch took 0.16195130348205566s
Availability | RDF dump link check for performing-arts.ch took 0.13662123680114746s
License | MR license check for performing-arts.ch took 0.1888594627380371s
License | HR license check for performing-arts.ch took 60.1392776966095s
Amount of data | Number of property check for performing-arts.ch took 0.5024232864379883s
Understandability | Number of label check for performing-arts.ch took 22.3683443069458s
Understandability | URI regex check for performing-arts.ch took 0.28895115852355957s
Understandability | Vocabs check for performing-arts.ch took 0.14330124855041504s
Verifiability | Authors check for performing-arts.ch took 0.2724268436431885s
Verifiability | Publishers check for performing-arts.ch took 0.1495356559753418s
Performance | Throughput check for performing-arts.ch took 10.694286823272705s
Amount of data | Check the number of entities for performing-arts.ch took 7.510185241699219e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.14989542961120605s
Interlinking | sameAs chians check for performing-arts.ch took 0.5558409690856934s
Interlinking | skos check for performing-arts.ch took 0.1725168228149414s
Interlinking | skos check for performing-arts.ch took 0.1611168384552002s
Timeliness | dataset update frequency check for performing-arts.ch took 0.15581750869750977s
Currency | Creation date check for performing-arts.ch took 0.3079109191894531s
Currency | Modification date check for performing-arts.ch took 0.35146355628967285s
Rep.Conc. | URIs length for performing-arts.ch took 20.34992027282715s
Interoperability | New vocabularies check for performing-arts.ch took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.14629912376403809s
Accuracy | Check Functional Property for performing-arts.ch took 0.1484513282775879s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.15592002868652344s
Accuracy | Check Empty annotation labels for performing-arts.ch took 11.141762495040894s
Accuracy | Check White space in annotation for performing-arts.ch took 2.583235025405884s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.937454462051392s
Consistency | Disjoint class check for performing-arts.ch took 0.19533085823059082s
Consistency | Check Misplaced properties for performing-arts.ch took 0.3786804676055908s
Consistency | Misplaced classes for performing-arts.ch took 8.642476320266724s
Consistency | Check Ontology hijacking for performing-arts.ch took 36.53746771812439s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 16539.42817211151s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.779021978378296s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.904392719268799s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.29680848121643066s
Security | Sign check for performing-arts.ch took 0.15865683555603027s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.4196770191192627s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.6047022342681885s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.02121138572692871s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 1.9073486328125e-06s
Believability | Calculation of trust value for performing-arts.ch took 7.867813110351562e-06s
INFO | --- Analysis for performing-arts.ch took 17453.780973911285s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.753190040588379s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.7353107929229736s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.2159347534179688e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for The-AA-Thesaurus took 13.251581907272339s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.813852310180664s
Availability | VoID file availability check for MiMoTextBase took 0.00041222572326660156s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.3062725067138672s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.1444091796875e-05s
Believability | Calculation of trust value for MiMoTextBase took 7.152557373046875e-06s
INFO | --- Analysis for MiMoTextBase took 7.274853229522705s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.4315605163574219s
Availability | VoID file availability check for National Library of Sweden took 0.0006313323974609375s
Extra | Recovery of all triples for National Library of Sweden took 15.538855075836182s
Performance | Total latancy measurement for National Library of Sweden took 1.0729732513427734s
Amount of data | Number of triples check for National Library of Sweden took 28.105340480804443s
Interoperability | New terms check for National Library of Sweden took 20.054353952407837s
Versatility | Languages check for National Library of Sweden took 0.2227613925933838s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.1915946006775s
Interpretability | RDF structures check for National Library of Sweden took 3.867960214614868s
Versatility | Serialization formats check for National Library of Sweden took 0.2853827476501465s
Availability | RDF dump link check for National Library of Sweden took 0.23900318145751953s
License | MR license check for National Library of Sweden took 0.38037538528442383s
License | HR license check for National Library of Sweden took 0.3279430866241455s
Amount of data | Number of property check for National Library of Sweden took 0.2160654067993164s
Understandability | Number of label check for National Library of Sweden took 0.7080180644989014s
Understandability | URI regex check for National Library of Sweden took 0.5592257976531982s
Understandability | Vocabs check for National Library of Sweden took 0.22185802459716797s
Verifiability | Authors check for National Library of Sweden took 0.2569286823272705s
Verifiability | Publishers check for National Library of Sweden took 0.2360532283782959s
Performance | Throughput check for National Library of Sweden took 10.687853813171387s
Amount of data | Check the number of entities for National Library of Sweden took 0.00012826919555664062s
Verifiability | Contribs. check for National Library of Sweden took 0.25730347633361816s
Interlinking | sameAs chians check for National Library of Sweden took 0.27383947372436523s
Interlinking | skos check for National Library of Sweden took 0.4563775062561035s
Interlinking | skos check for National Library of Sweden took 0.2001347541809082s
Timeliness | dataset update frequency check for National Library of Sweden took 0.23357844352722168s
Currency | Creation date check for National Library of Sweden took 0.45946359634399414s
Currency | Modification date check for National Library of Sweden took 0.43180274963378906s
Rep.Conc. | URIs length for National Library of Sweden took 82.34809875488281s
Interoperability | New vocabularies check for National Library of Sweden took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.2115311622619629s
Accuracy | Check Functional Property for National Library of Sweden took 0.2171030044555664s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.20366621017456055s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.27633023262023926s
Consistency | Disjoint class check for National Library of Sweden took 0.2442312240600586s
Consistency | Check Misplaced properties for National Library of Sweden took 60.98663520812988s
Consistency | Misplaced classes for National Library of Sweden took 1.1650478839874268s
Consistency | Check Ontology hijacking for National Library of Sweden took 6.605190277099609s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.3106303215026855s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 62.07281827926636s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.28510618209838867s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.4084632396697998s
Security | Sign check for National Library of Sweden took 0.3831799030303955s
Availability | Check URIs Dereferenciability for National Library of Sweden took 9.790292978286743s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 1.279721736907959s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.0967254638671875e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.430511474609375e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.7642974853515625e-05s
INFO | --- Analysis for NLS took 1398.7199470996857s
Availability | SPARQL endpoint availability check for Japan Search took 1.7087805271148682s
Availability | VoID file availability check for Japan Search took 0.0002830028533935547s
Extra | Recovery of all triples for Japan Search took 3.2000865936279297s
Performance | Total latancy measurement for Japan Search took 1.4622092247009277s
Amount of data | Number of triples check for Japan Search took 6.5561363697052s
Interoperability | New terms check for Japan Search took 3.274073600769043s
Versatility | Languages check for Japan Search took 0.2837221622467041s
Interpretability | Number of blank nodes check for Japan Search took 10.789487838745117s
Interpretability | RDF structures check for Japan Search took 0.3983769416809082s
Versatility | Serialization formats check for Japan Search took 0.4138777256011963s
Availability | RDF dump link check for Japan Search took 0.338148832321167s
License | MR license check for Japan Search took 1.1138033866882324s
License | HR license check for Japan Search took 10.697813749313354s
Amount of data | Number of property check for Japan Search took 0.2893657684326172s
Understandability | Number of label check for Japan Search took 3.325047731399536s
Understandability | URI regex check for Japan Search took 0.5229802131652832s
Understandability | Vocabs check for Japan Search took 0.30904388427734375s
Verifiability | Authors check for Japan Search took 0.3154294490814209s
Verifiability | Publishers check for Japan Search took 0.29578232765197754s
Performance | Throughput check for Japan Search took 11.27140736579895s
Amount of data | Check the number of entities for Japan Search took 7.224082946777344e-05s
Verifiability | Contribs. check for Japan Search took 0.34040331840515137s
Interlinking | sameAs chians check for Japan Search took 0.29554224014282227s
Interlinking | skos check for Japan Search took 0.46201205253601074s
Interlinking | skos check for Japan Search took 0.26369380950927734s
Timeliness | dataset update frequency check for Japan Search took 0.31328558921813965s
Currency | Creation date check for Japan Search took 0.6313741207122803s
Currency | Modification date check for Japan Search took 0.586226224899292s
Rep.Conc. | URIs length for Japan Search took 13.730695724487305s
Interoperability | New vocabularies check for Japan Search took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.26137495040893555s
Accuracy | Check Functional Property for Japan Search took 0.36414599418640137s
Accuracy | Check Inverse Functional Property for Japan Search took 0.363750696182251s
Accuracy | Check Empty annotation labels for Japan Search took 0.5671443939208984s
Accuracy | Check White space in annotation for Japan Search took 0.03216409683227539s
Accuracy | Check Datatype consistency for Japan Search took 0.030879497528076172s
Consistency | Disjoint class check for Japan Search took 0.36535000801086426s
Consistency | Check Misplaced properties for Japan Search took 11.190152645111084s
Consistency | Misplaced classes for Japan Search took 0.40285634994506836s
Consistency | Check Ontology hijacking for Japan Search took 1.8364472389221191s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3530323505401611s
Consistency | Check Invalid usage of undefined properties for Japan Search took 12.981602430343628s
Conciseness | Check Extensional conciseness for Japan Search took 0.034421682357788086s
Conciseness | Check Intensional conciseness for Japan Search took 0.2991759777069092s
Security | Sign check for Japan Search took 0.2897963523864746s
Availability | Check URIs Dereferenciability for Japan Search took 9.65945291519165s
Completeness | Calculation of interlinking completeness for Japan Search took 0.2691841125488281s
Reputation | Calculation of the PageRank for Japan Search took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.1920928955078125e-06s
Believability | Calculation of trust value for Japan Search took 8.106231689453125e-06s
INFO | --- Analysis for Japan-Search took 395.96585607528687s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 0.9159114360809326s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.2579689025878906s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.020843505859375s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.2636184692382812e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 8.344650268554688e-06s
INFO | --- Analysis for Rijksmuseum took 4.726171493530273s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.6903679370880127s
Availability | VoID file availability check for Finnish Public Libraries took 0.0005695819854736328s
Extra | Recovery of all triples for Finnish Public Libraries took 19.71698260307312s
Performance | Total latancy measurement for Finnish Public Libraries took 1.1231379508972168s
Amount of data | Number of triples check for Finnish Public Libraries took 60.12713408470154s
Interoperability | New terms check for Finnish Public Libraries took 17.526918649673462s
Versatility | Languages check for Finnish Public Libraries took 60.192681312561035s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.93591117858887s
Interpretability | RDF structures check for Finnish Public Libraries took 0.3898911476135254s
Versatility | Serialization formats check for Finnish Public Libraries took 0.2690773010253906s
Availability | RDF dump link check for Finnish Public Libraries took 0.10356378555297852s
License | MR license check for Finnish Public Libraries took 0.4570424556732178s
License | HR license check for Finnish Public Libraries took 56.37840032577515s
Amount of data | Number of property check for Finnish Public Libraries took 0.32892727851867676s
Understandability | Number of label check for Finnish Public Libraries took 15.114887714385986s
Understandability | URI regex check for Finnish Public Libraries took 0.40872645378112793s
Understandability | Vocabs check for Finnish Public Libraries took 0.3532984256744385s
Verifiability | Authors check for Finnish Public Libraries took 0.47699618339538574s
Verifiability | Publishers check for Finnish Public Libraries took 0.3150615692138672s
Performance | Throughput check for Finnish Public Libraries took 11.58981204032898s
Amount of data | Check the number of entities for Finnish Public Libraries took 9.083747863769531e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.12142586708068848s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.5204331874847412s
Interlinking | skos check for Finnish Public Libraries took 0.11206912994384766s
Interlinking | skos check for Finnish Public Libraries took 0.13451313972473145s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.29292845726013184s
Currency | Creation date check for Finnish Public Libraries took 0.4020652770996094s
Currency | Modification date check for Finnish Public Libraries took 0.239959716796875s
Rep.Conc. | URIs length for Finnish Public Libraries took 85.77685880661011s
Interoperability | New vocabularies check for Finnish Public Libraries took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.21351408958435059s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 9.717700004577637s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.224947214126587s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.489876747131348s
Consistency | Disjoint class check for Finnish Public Libraries took 0.28180480003356934s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.51108956336975s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 18.304223775863647s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.6285886764526367s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.73854446411133s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.782975196838379s
Security | Sign check for Finnish Public Libraries took 0.30313968658447266s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.0148155689239502s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 1.3281629085540771s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.02092123031616211s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.8596649169921875e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 1.9073486328125e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 8.58306884765625e-06s
INFO | --- Analysis for FI-Library took 700.0203223228455s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 2.6303844451904297s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.7015929222106934s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.02099323272705078s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.4066696166992188e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 8.58306884765625e-06s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 8.439457178115845s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.4361481666564941s
Availability | VoID file availability check for National Library Netherlands took 0.0005733966827392578s
Extra | Recovery of all triples for National Library Netherlands took 1.791560173034668s
Performance | Total latancy measurement for National Library Netherlands took 0.7838649749755859s
Amount of data | Number of triples check for National Library Netherlands took 0.6223263740539551s
Interoperability | New terms check for National Library Netherlands took 5.030235767364502s
Versatility | Languages check for National Library Netherlands took 58.1531708240509s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.18034648895263672s
Interpretability | RDF structures check for National Library Netherlands took 0.5321750640869141s
Versatility | Serialization formats check for National Library Netherlands took 0.1862180233001709s
Availability | RDF dump link check for National Library Netherlands took 0.14310002326965332s
License | MR license check for National Library Netherlands took 0.43466687202453613s
License | HR license check for National Library Netherlands took 58.12719416618347s
Amount of data | Number of property check for National Library Netherlands took 0.15115928649902344s
Understandability | Number of label check for National Library Netherlands took 13.699463129043579s
Understandability | URI regex check for National Library Netherlands took 0.31030726432800293s
Understandability | Vocabs check for National Library Netherlands took 0.14922094345092773s
Verifiability | Authors check for National Library Netherlands took 0.161118745803833s
Verifiability | Publishers check for National Library Netherlands took 0.15010857582092285s
Performance | Throughput check for National Library Netherlands took 10.633401155471802s
Amount of data | Check the number of entities for National Library Netherlands took 7.677078247070312e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.1663684844970703s
Interlinking | sameAs chians check for National Library Netherlands took 0.580578088760376s
Interlinking | skos check for National Library Netherlands took 0.1817789077758789s
Interlinking | skos check for National Library Netherlands took 0.16456818580627441s
Timeliness | dataset update frequency check for National Library Netherlands took 0.16204380989074707s
Currency | Creation date check for National Library Netherlands took 0.32239770889282227s
Currency | Modification date check for National Library Netherlands took 0.3479902744293213s
Rep.Conc. | URIs length for National Library Netherlands took 4.849050045013428s
Interoperability | New vocabularies check for National Library Netherlands took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.1508316993713379s
Accuracy | Check Functional Property for National Library Netherlands took 0.1849820613861084s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.18891310691833496s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.5966424942016602s
Accuracy | Check White space in annotation for National Library Netherlands took 0.02536320686340332s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.028933286666870117s
Consistency | Disjoint class check for National Library Netherlands took 0.25585436820983887s
Consistency | Check Misplaced properties for National Library Netherlands took 3.488898277282715s
Consistency | Check Ontology hijacking for National Library Netherlands took 2.047128438949585s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 2.135347366333008s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.4954547882080078s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.03456592559814453s
Security | Sign check for National Library Netherlands took 0.14967584609985352s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1699.7887015342712s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.6927399635314941s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.023447751998901367s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 3.337860107421875e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.3365020751953125e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for National Library Netherlands took 8.58306884765625e-06s
INFO | --- Analysis for National-Library-Netherlands took 1894.9891519546509s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.511908769607544s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.27625417709350586s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.02221202850341797s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.3828277587890625e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 7.3909759521484375e-06s
INFO | --- Analysis for Antique-Renaissance took 5.783188104629517s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 5.6495630741119385s
Availability | VoID file availability check for ARTSDATA.CA took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.3011820316314697s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.3113021850585938e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 7.152557373046875e-06s
INFO | --- Analysis for ARTSDATA-CA took 11.611062288284302s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.26535725593566895s
Availability | VoID file availability check for Architecture of Knowledge took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.28819727897644043s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.239776611328125e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 8.344650268554688e-06s
INFO | --- Analysis for ArCo took 3.4636189937591553s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.30266475677490234s
Availability | VoID file availability check for ConfermentSampo took 0.00028133392333984375s
Extra | Recovery of all triples for ConfermentSampo took 174.71451616287231s
Performance | Total latancy measurement for ConfermentSampo took 0.9189138412475586s
Amount of data | Number of triples check for ConfermentSampo took 12.175742387771606s
Interoperability | New terms check for ConfermentSampo took 4.6349005699157715s
Versatility | Languages check for ConfermentSampo took 30.688842296600342s
Interpretability | Number of blank nodes check for ConfermentSampo took 8.00381088256836s
Security | Check HTTPS for ConfermentSampo took 0.42296290397644043s
Interpretability | RDF structures check for ConfermentSampo took 0.22133874893188477s
Versatility | Serialization formats check for ConfermentSampo took 0.22068238258361816s
Availability | RDF dump link check for ConfermentSampo took 3.2453339099884033s
License | MR license check for ConfermentSampo took 0.21817660331726074s
License | HR license check for ConfermentSampo took 0.4863436222076416s
Amount of data | Number of property check for ConfermentSampo took 0.20467066764831543s
Understandability | Number of label check for ConfermentSampo took 17.8018856048584s
Understandability | URI regex check for ConfermentSampo took 0.37483930587768555s
Understandability | Vocabs check for ConfermentSampo took 0.1797633171081543s
Verifiability | Authors check for ConfermentSampo took 0.19764161109924316s
Verifiability | Publishers check for ConfermentSampo took 0.21627259254455566s
Performance | Throughput check for ConfermentSampo took 10.682064056396484s
Amount of data | Check the number of entities for ConfermentSampo took 4.161213159561157s
Verifiability | Contribs. check for ConfermentSampo took 0.18152213096618652s
Interlinking | sameAs chians check for ConfermentSampo took 0.610985279083252s
Interlinking | skos check for ConfermentSampo took 0.20507335662841797s
Interlinking | skos check for ConfermentSampo took 0.1766657829284668s
Timeliness | dataset update frequency check for ConfermentSampo took 0.2131664752960205s
Currency | Creation date check for ConfermentSampo took 0.38402557373046875s
Currency | Modification date check for ConfermentSampo took 0.3710143566131592s
Rep.Conc. | URIs length for ConfermentSampo took 97.06313943862915s
Interoperability | New vocabularies check for ConfermentSampo took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.19880342483520508s
Accuracy | Check Functional Property for ConfermentSampo took 0.20725464820861816s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.18231439590454102s
Accuracy | Check Empty annotation labels for ConfermentSampo took 61.0162296295166s
Accuracy | Check White space in annotation for ConfermentSampo took 3.0560333728790283s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.224912881851196s
Consistency | Disjoint class check for ConfermentSampo took 0.18261480331420898s
Consistency | Check Misplaced properties for ConfermentSampo took 6.866413354873657s
Consistency | Check Ontology hijacking for ConfermentSampo took 65.43141055107117s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.477874994277954s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.583665370941162s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.858555555343628s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.24471259117126465s
Security | Sign check for ConfermentSampo took 0.19435405731201172s
Availability | Check URIs Dereferenciability for ConfermentSampo took 2.609830141067505s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.3897068500518799s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.1682510375976562e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 1.9073486328125e-06s
Believability | Calculation of trust value for ConfermentSampo took 8.344650268554688e-06s
INFO | --- Analysis for ConfermentSampo took 666.028126001358s
Availability | SPARQL endpoint availability check for Museum Finland took 0.4465155601501465s
Availability | VoID file availability check for Museum Finland took 0.00028014183044433594s
Extra | Recovery of all triples for Museum Finland took 48.766674518585205s
Performance | Total latancy measurement for Museum Finland took 0.8778681755065918s
Amount of data | Number of triples check for Museum Finland took 0.3774104118347168s
Interoperability | New terms check for Museum Finland took 2.080512523651123s
Versatility | Languages check for Museum Finland took 5.874964237213135s
Interpretability | Number of blank nodes check for Museum Finland took 0.33725953102111816s
Security | Check HTTPS for Museum Finland took 0.2671804428100586s
Interpretability | RDF structures check for Museum Finland took 0.4833676815032959s
Versatility | Serialization formats check for Museum Finland took 0.20152592658996582s
Availability | RDF dump link check for Museum Finland took 0.18486309051513672s
License | MR license check for Museum Finland took 0.16659879684448242s
License | HR license check for Museum Finland took 0.3478891849517822s
Amount of data | Number of property check for Museum Finland took 0.1913156509399414s
Understandability | Number of label check for Museum Finland took 0.3167405128479004s
Understandability | URI regex check for Museum Finland took 0.3471987247467041s
Understandability | Vocabs check for Museum Finland took 0.17081451416015625s
Verifiability | Authors check for Museum Finland took 0.19745135307312012s
Verifiability | Publishers check for Museum Finland took 0.17604923248291016s
Performance | Throughput check for Museum Finland took 10.990770816802979s
Amount of data | Check the number of entities for Museum Finland took 7.414817810058594e-05s
Verifiability | Contribs. check for Museum Finland took 0.15696358680725098s
Interlinking | sameAs chians check for Museum Finland took 0.17041754722595215s
Interlinking | skos check for Museum Finland took 0.1708226203918457s
Interlinking | skos check for Museum Finland took 0.16815638542175293s
Timeliness | dataset update frequency check for Museum Finland took 0.15772151947021484s
Currency | Creation date check for Museum Finland took 0.359677791595459s
Currency | Modification date check for Museum Finland took 0.3820643424987793s
Rep.Conc. | URIs length for Museum Finland took 7.833572626113892s
Interoperability | New vocabularies check for Museum Finland took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.19158220291137695s
Accuracy | Check Functional Property for Museum Finland took 0.16653871536254883s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.17796683311462402s
Accuracy | Check Empty annotation labels for Museum Finland took 1.607008934020996s
Accuracy | Check White space in annotation for Museum Finland took 0.06301379203796387s
Accuracy | Check Datatype consistency for Museum Finland took 0.9909248352050781s
Consistency | Disjoint class check for Museum Finland took 0.1644899845123291s
Consistency | Check Misplaced properties for Museum Finland took 0.6334526538848877s
Consistency | Check Ontology hijacking for Museum Finland took 2.907160520553589s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.5700631141662598s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.7354650497436523s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6599528789520264s
Conciseness | Check Intensional conciseness for Museum Finland took 0.28945016860961914s
Security | Sign check for Museum Finland took 0.1759040355682373s
Availability | Check URIs Dereferenciability for Museum Finland took 3221.8297481536865s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.7816665172576904s
Reputation | Calculation of the PageRank for Museum Finland took 0.023234128952026367s
Interlinking | Calculation of Degree of Connection for Museum Finland took 0.00010991096496582031s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.1682510375976562e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 1.1920928955078125e-06s
Believability | Calculation of trust value for Museum Finland took 1.3113021850585938e-05s
INFO | --- Analysis for FI-Museum took 3333.153256416321s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.20735645294189453s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0003552436828613281s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 161.13715434074402s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.8802719116210938s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 37.515639781951904s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.920216083526611s
Versatility | Languages check for Mapping Manuscript Migrations took 82.29411339759827s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 31.85474181175232s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.43297791481018066s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.205610990524292s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.20455408096313477s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.1661076545715332s
License | MR license check for Mapping Manuscript Migrations took 0.21271872520446777s
License | HR license check for Mapping Manuscript Migrations took 1.8585765361785889s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.2071678638458252s
Understandability | Number of label check for Mapping Manuscript Migrations took 78.45295190811157s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3695101737976074s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.18066692352294922s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.19943594932556152s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.19848084449768066s
Performance | Throughput check for Mapping Manuscript Migrations took 10.70997667312622s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0737583637237549s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.224900484085083s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.16205477714538574s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16315102577209473s
Interlinking | skos check for Mapping Manuscript Migrations took 0.17562055587768555s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.1842799186706543s
Currency | Creation date check for Mapping Manuscript Migrations took 0.3361794948577881s
Currency | Modification date check for Mapping Manuscript Migrations took 0.33335113525390625s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 95.7500422000885s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.19538593292236328s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.1639270782470703s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.16845226287841797s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 56.87251353263855s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.459198236465454s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.8709070682525635s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.20616364479064941s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 23.1458899974823s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 65.7271614074707s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.6630682945251465s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.6867504119873047s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.9048242568969727s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.27655601501464844s
Security | Sign check for Mapping Manuscript Migrations took 0.20488476753234863s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1723.0147516727448s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.938164234161377s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.022405147552490234s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 7.557868957519531e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.621246337890625e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 2.1457672119140625e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 8.821487426757812e-06s
INFO | --- Analysis for MMM took 2462.2866735458374s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.35889482498168945s
Availability | VoID file availability check for Semantic Kalevala took 0.000324249267578125s
Extra | Recovery of all triples for Semantic Kalevala took 54.03139042854309s
Performance | Total latancy measurement for Semantic Kalevala took 0.8558402061462402s
Amount of data | Number of triples check for Semantic Kalevala took 0.4695115089416504s
Interoperability | New terms check for Semantic Kalevala took 2.015925168991089s
Versatility | Languages check for Semantic Kalevala took 0.9868519306182861s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.4271669387817383s
Security | Check HTTPS for Semantic Kalevala took 0.414353609085083s
Interpretability | RDF structures check for Semantic Kalevala took 0.2234632968902588s
Versatility | Serialization formats check for Semantic Kalevala took 0.19484543800354004s
Availability | RDF dump link check for Semantic Kalevala took 0.16769862174987793s
License | MR license check for Semantic Kalevala took 0.1700429916381836s
License | HR license check for Semantic Kalevala took 1.0260283946990967s
Amount of data | Number of property check for Semantic Kalevala took 0.20982933044433594s
Understandability | Number of label check for Semantic Kalevala took 0.3611288070678711s
Understandability | URI regex check for Semantic Kalevala took 0.33340907096862793s
Understandability | Vocabs check for Semantic Kalevala took 0.17099213600158691s
Verifiability | Authors check for Semantic Kalevala took 0.17946267127990723s
Verifiability | Publishers check for Semantic Kalevala took 0.165330171585083s
Performance | Throughput check for Semantic Kalevala took 11.066603422164917s
Amount of data | Check the number of entities for Semantic Kalevala took 7.05718994140625e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.17784547805786133s
Interlinking | sameAs chians check for Semantic Kalevala took 0.2067570686340332s
Interlinking | skos check for Semantic Kalevala took 0.28533339500427246s
Interlinking | skos check for Semantic Kalevala took 0.16147184371948242s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.17859244346618652s
Currency | Creation date check for Semantic Kalevala took 0.38018274307250977s
Currency | Modification date check for Semantic Kalevala took 0.356550931930542s
Rep.Conc. | URIs length for Semantic Kalevala took 13.139849424362183s
Interoperability | New vocabularies check for Semantic Kalevala took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.20594072341918945s
Accuracy | Check Functional Property for Semantic Kalevala took 0.1945781707763672s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.16333270072937012s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 6.52268123626709s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.3021275997161865s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.4577844142913818s
Consistency | Disjoint class check for Semantic Kalevala took 0.17256999015808105s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7965385913848877s
Consistency | Check Ontology hijacking for Semantic Kalevala took 3.630838632583618s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.5421504974365234s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.7475574016571045s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.9325206279754639s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.4924774169921875s
Security | Sign check for Semantic Kalevala took 0.1742548942565918s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 3411.9147119522095s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.7099814414978027s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.6335318088531494s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 2.1457672119140625e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.3589859008789062e-05s
INFO | --- Analysis for Semantic-Kalevala took 3541.1229820251465s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.88057541847229s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0006070137023925781s
Extra | Recovery of all triples for Smithsonian American Art Museum took 282.57295274734497s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.032339334487915s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.588198184967041s
Interoperability | New terms check for Smithsonian American Art Museum took 2.880462169647217s
Versatility | Languages check for Smithsonian American Art Museum took 29.28101134300232s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5973525047302246s
Security | Check HTTPS for Smithsonian American Art Museum took 0.3678257465362549s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.6301946640014648s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6173286437988281s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.6078963279724121s
License | MR license check for Smithsonian American Art Museum took 0.5975911617279053s
License | HR license check for Smithsonian American Art Museum took 26.08501148223877s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5902793407440186s
Understandability | Number of label check for Smithsonian American Art Museum took 0.6087319850921631s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1706156730651855s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.6068253517150879s
Verifiability | Authors check for Smithsonian American Art Museum took 0.6389265060424805s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.6135258674621582s
Performance | Throughput check for Smithsonian American Art Museum took 12.211808681488037s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 6.937980651855469e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.590282678604126s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5900082588195801s
Interlinking | skos check for Smithsonian American Art Museum took 0.6029460430145264s
Interlinking | skos check for Smithsonian American Art Museum took 0.5864121913909912s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.6612789630889893s
Currency | Creation date check for Smithsonian American Art Museum took 1.2705671787261963s
Currency | Modification date check for Smithsonian American Art Museum took 1.1877024173736572s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 109.18408584594727s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.6005678176879883s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 20.01882576942444s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5305027961730957s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.346061944961548s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.6247303485870361s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 4.331777334213257s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 97.54440712928772s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.6344926357269287s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 5.04491662979126s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.8947994709014893s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6357810497283936s
Security | Sign check for Smithsonian American Art Museum took 0.5949914455413818s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.3642578125s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.9019808769226074s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.026522397994995117s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.384185791015625e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 1.0013580322265625e-05s
INFO | --- Analysis for Smithsonian took 717.4562749862671s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.20691132545471191s
Availability | VoID file availability check for Zeri Photo Archive took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.27683210372924805s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.020812273025512695s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.4066696166992188e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 8.58306884765625e-06s
INFO | --- Analysis for Zeri-Photo-Archive took 9.224261045455933s
Availability | SPARQL endpoint availability check for Archives Hub took 20.45110249519348s
Availability | VoID file availability check for Archives Hub took 0.00033402442932128906s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.29712414741516113s
Reputation | Calculation of the PageRank for Archives Hub took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for Archives Hub took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.1444091796875e-05s
Believability | Calculation of trust value for Archives Hub took 1.2159347534179688e-05s
INFO | --- Analysis for Archives-Hub took 53.967602014541626s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.53704833984375s
Availability | VoID file availability check for Yale centre of British Art took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.26033878326416016s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.1682510375976562e-05s
Believability | Calculation of trust value for Yale centre of British Art took 8.344650268554688e-06s
INFO | --- Analysis for Yale took 4.5046656131744385s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 260.76809668540955s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.7158639430999756s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 2.09808349609375e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.1205673217773438e-05s
INFO | --- Analysis for ADL took 535.7158005237579s
Availability | SPARQL endpoint availability check for MusicKG took 0.797501802444458s
Availability | VoID file availability check for MusicKG took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for MusicKG took 0.2960672378540039s
Reputation | Calculation of the PageRank for MusicKG took 0.0212247371673584s
Interlinking | Calculation of Degree of Connection for MusicKG took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0008356571197509766s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.1920928955078125e-05s
Believability | Calculation of trust value for MusicKG took 9.5367431640625e-06s
INFO | --- Analysis for MusicKG took 5.42737078666687s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.8674812316894531s
Availability | VoID file availability check for CIDOC-CRM took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.2725095748901367s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.2159347534179688e-05s
Believability | Calculation of trust value for CIDOC-CRM took 7.152557373046875e-06s
INFO | --- Analysis for CIDOC-CRM took 4.478142499923706s
Availability | SPARQL endpoint availability check for Mondis took 0.43735384941101074s
Availability | VoID file availability check for Mondis took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Mondis took 0.2972586154937744s
Reputation | Calculation of the PageRank for Mondis took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for Mondis took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.1682510375976562e-05s
Believability | Calculation of trust value for Mondis took 1.6927719116210938e-05s
INFO | --- Analysis for Mondis took 3.960264205932617s
Availability | SPARQL endpoint availability check for DigitalNZ took 2.321460485458374s
Availability | VoID file availability check for DigitalNZ took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.28629541397094727s
Reputation | Calculation of the PageRank for DigitalNZ took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.2159347534179688e-05s
Believability | Calculation of trust value for DigitalNZ took 7.3909759521484375e-06s
INFO | --- Analysis for DigitalNZ took 5.4199442863464355s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.2006359100341797s
Availability | VoID file availability check for Fondazione Zeri took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.26087117195129395s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.1920928955078125e-05s
Believability | Calculation of trust value for Fondazione Zeri took 7.867813110351562e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.215728998184204s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.948538064956665s
Availability | VoID file availability check for Digital Public Library of America took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.297299861907959s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.1920928955078125e-05s
Believability | Calculation of trust value for Digital Public Library of America took 8.344650268554688e-06s
INFO | --- Analysis for Library-of-America took 4.7899580001831055s
Availability | SPARQL endpoint availability check for Auckland Museum took 2.5066192150115967s
Availability | VoID file availability check for Auckland Museum took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.27812981605529785s
Reputation | Calculation of the PageRank for Auckland Museum took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.2636184692382812e-05s
Believability | Calculation of trust value for Auckland Museum took 6.4373016357421875e-06s
INFO | --- Analysis for Auckland-Museum took 7.280843496322632s
Availability | SPARQL endpoint availability check for National Library of Spain took 1.8834991455078125s
Availability | VoID file availability check for National Library of Spain took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.271451473236084s
Reputation | Calculation of the PageRank for National Library of Spain took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.6450881958007812e-05s
Believability | Calculation of trust value for National Library of Spain took 5.9604644775390625e-06s
INFO | --- Analysis for BNE took 4.860198974609375s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.484736442565918s
Availability | VoID file availability check for National Library of Korea took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.26021647453308105s
Reputation | Calculation of the PageRank for National Library of Korea took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.239776611328125e-05s
Believability | Calculation of trust value for National Library of Korea took 1.1682510375976562e-05s
INFO | --- Analysis for Korea-Library took 5.326997995376587s
Availability | SPARQL endpoint availability check for The State Russian Museum took 2.565722942352295s
Availability | VoID file availability check for The State Russian Museum took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.23630261421203613s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020900726318359375s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.1205673217773438e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.0013580322265625e-05s
INFO | --- Analysis for Russian-Museum took 5.565245866775513s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.9354238510131836s
Availability | VoID file availability check for National Library of Scotland took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.2628602981567383s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.020815372467041016s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.3113021850585938e-05s
Believability | Calculation of trust value for National Library of Scotland took 7.62939453125e-06s
INFO | --- Analysis for National-Library-of-Scotland took 7.385303258895874s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.3160998821258545s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.2758626937866211s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.3589859008789062e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 7.152557373046875e-06s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.292983055114746s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.22191429138183594s
Availability | VoID file availability check for OntoComedySources took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.25898122787475586s
Reputation | Calculation of the PageRank for OntoComedySources took 0.020758867263793945s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.3113021850585938e-05s
Believability | Calculation of trust value for OntoComedySources took 7.62939453125e-06s
INFO | --- Analysis for OntoComedySources took 4.149391412734985s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.2181079387664795s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.26300883293151855s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.021060705184936523s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.3589859008789062e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 8.58306884765625e-06s
INFO | --- Analysis for OntoCeramic-2.0 took 4.708474397659302s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.17032337188720703s
Availability | VoID file availability check for SaintGall Ontology took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.2660956382751465s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.021274328231811523s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0010721683502197266s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.4543533325195312e-05s
Believability | Calculation of trust value for SaintGall Ontology took 9.5367431640625e-06s
INFO | --- Analysis for SaintGall-Ontology took 3.065117120742798s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.8976387977600098s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0007750988006591797s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.25968289375305176s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.023093223571777344s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0011911392211914062s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.5497207641601562e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 4.019637584686279s
Availability | SPARQL endpoint availability check for ICON took 0.293323278427124s
Availability | VoID file availability check for ICON took 0.0008213520050048828s
Completeness | Calculation of interlinking completeness for ICON took 0.24654769897460938s
Reputation | Calculation of the PageRank for ICON took 0.020739316940307617s
Interlinking | Calculation of Degree of Connection for ICON took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for ICON took 1.2636184692382812e-05s
Believability | Calculation of trust value for ICON took 9.298324584960938e-06s
INFO | --- Analysis for ICON took 4.133977651596069s
Availability | SPARQL endpoint availability check for Polifonia took 0.2654244899749756s
Availability | VoID file availability check for Polifonia took 0.0007593631744384766s
Completeness | Calculation of interlinking completeness for Polifonia took 0.25592827796936035s
Reputation | Calculation of the PageRank for Polifonia took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0008189678192138672s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.2874603271484375e-05s
Believability | Calculation of trust value for Polifonia took 8.821487426757812e-06s
INFO | --- Analysis for Polifonia took 4.370432615280151s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.24065470695495605s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.24897289276123047s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.1682510375976562e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 1.1444091796875e-05s
INFO | --- Analysis for Atlas-of-Paths took 3.8692243099212646s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.21760892868041992s
Availability | VoID file availability check for Music Note Ontology took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.27037906646728516s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.020644426345825195s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.3828277587890625e-05s
Believability | Calculation of trust value for Music Note Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Music-Note-Ontology took 15.637431383132935s
Availability | SPARQL endpoint availability check for HaMSE took 0.21460366249084473s
Availability | VoID file availability check for HaMSE took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for HaMSE took 0.2541475296020508s
Reputation | Calculation of the PageRank for HaMSE took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.239776611328125e-05s
Believability | Calculation of trust value for HaMSE took 7.3909759521484375e-06s
INFO | --- Analysis for HaMSE took 6.251307487487793s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.11481618881225586s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.253373384475708s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.02116680145263672s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.1920928955078125e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 8.821487426757812e-06s
INFO | --- Analysis for FOod took 3.3202319145202637s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.5890073776245117s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.2781062126159668s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.02119159698486328s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.3589859008789062e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 8.106231689453125e-06s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 4.974648952484131s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 2.4293053150177s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.25626540184020996s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.3113021850585938e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for ARIADNE took 6.59990382194519s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.3641242980957031s
Availability | VoID file availability check for Nomisma.org  took 0.0006401538848876953s
Extra | Recovery of all triples for Nomisma.org  took 341.3933343887329s
Performance | Total latancy measurement for Nomisma.org  took 1.3791277408599854s
Amount of data | Number of triples check for Nomisma.org  took 39.04383182525635s
Interoperability | New terms check for Nomisma.org  took 7.007704496383667s
Versatility | Languages check for Nomisma.org  took 95.39940333366394s
Interpretability | Number of blank nodes check for Nomisma.org  took 35.820536375045776s
Security | Check HTTPS for Nomisma.org  took 0.6611685752868652s
Interpretability | RDF structures check for Nomisma.org  took 0.30770397186279297s
Versatility | Serialization formats check for Nomisma.org  took 0.2978842258453369s
Availability | RDF dump link check for Nomisma.org  took 987.7958564758301s
License | MR license check for Nomisma.org  took 0.3399314880371094s
License | HR license check for Nomisma.org  took 58.181692123413086s
Amount of data | Number of property check for Nomisma.org  took 0.3222193717956543s
Understandability | Number of label check for Nomisma.org  took 6.330935001373291s
Understandability | URI regex check for Nomisma.org  took 0.5969030857086182s
Understandability | Vocabs check for Nomisma.org  took 0.2593231201171875s
Verifiability | Authors check for Nomisma.org  took 0.25993776321411133s
Verifiability | Publishers check for Nomisma.org  took 0.2815701961517334s
Performance | Throughput check for Nomisma.org  took 10.656979322433472s
Amount of data | Check the number of entities for Nomisma.org  took 61.28820776939392s
Verifiability | Contribs. check for Nomisma.org  took 0.29785943031311035s
Interlinking | sameAs chians check for Nomisma.org  took 0.29944825172424316s
Interlinking | skos check for Nomisma.org  took 4.199326992034912s
Interlinking | skos check for Nomisma.org  took 0.47775816917419434s
Timeliness | dataset update frequency check for Nomisma.org  took 0.26244187355041504s
Currency | Creation date check for Nomisma.org  took 0.559678316116333s
Currency | Modification date check for Nomisma.org  took 0.3066987991333008s
Rep.Conc. | URIs length for Nomisma.org  took 173.34948134422302s
Interoperability | New vocabularies check for Nomisma.org  took 4.100799560546875e-05s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.2876105308532715s
Accuracy | Check Functional Property for Nomisma.org  took 0.31242823600769043s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.27218055725097656s
Accuracy | Check Empty annotation labels for Nomisma.org  took 109.91707301139832s
Accuracy | Check White space in annotation for Nomisma.org  took 2.8087031841278076s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.65316367149353s
Consistency | Disjoint class check for Nomisma.org  took 0.27956104278564453s
Consistency | Check Misplaced properties for Nomisma.org  took 25.019310474395752s
Consistency | Check Ontology hijacking for Nomisma.org  took 126.77930879592896s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 2.0068538188934326s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 25.946017026901245s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.807140350341797s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.3056321144104004s
Security | Sign check for Nomisma.org  took 0.2886016368865967s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1871.406653881073s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.623412847518921s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.024344682693481445s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 0.00011134147644042969s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 0.0001087188720703125s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.9073486328125e-06s
Believability | Calculation of trust value for Nomisma.org  took 9.059906005859375e-06s
INFO | --- Analysis for nomisma_org took 8011.017990112305s
Availability | SPARQL endpoint availability check for Discogs in RDF took 5.030632019042969e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.24441766738891602s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020796537399291992s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0008716583251953125s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 0.00010180473327636719s
Believability | Calculation of trust value for Discogs in RDF took 8.58306884765625e-06s
INFO | --- Analysis for data-incubator-discogs took 8.659456729888916s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.553794860839844e-05s
Availability | VoID file availability check for Enslaved.org took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2806968688964844s
Reputation | Calculation of the PageRank for Enslaved.org took 0.021056652069091797s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.123283386230469e-05s
Believability | Calculation of trust value for Enslaved.org took 8.58306884765625e-06s
INFO | --- Analysis for enslaved.org took 5.812973499298096s
Availability | SPARQL endpoint availability check for EventKG took 4.601478576660156e-05s
Availability | VoID file availability check for EventKG took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for EventKG took 0.26347923278808594s
Reputation | Calculation of the PageRank for EventKG took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for EventKG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EventKG took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.654594421386719e-05s
Believability | Calculation of trust value for EventKG took 8.344650268554688e-06s
INFO | --- Analysis for eventkg took 6.7311530113220215s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.2729623317718506s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0007052421569824219s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 48.27889680862427s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.4350545406341553s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 2.0685925483703613s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.8143699169158936s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 5.353686571121216s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.405665397644043s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.08465719223022461s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.0943915843963623s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.07931876182556152s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.09615349769592285s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.0898284912109375s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.09409332275390625s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.09131717681884766s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.1807701587677002s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.08760190010070801s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.08655190467834473s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.09552812576293945s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.460403680801392s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 0.00011134147644042969s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.08707761764526367s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.08796215057373047s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08494687080383301s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.07973003387451172s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.09571981430053711s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.18195009231567383s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.17609596252441406s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 21.9183406829834s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.08144164085388184s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.09276819229125977s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.08426427841186523s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.9205121994018555s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.09050250053405762s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 3.22367000579834s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 7.1635565757751465s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.48038649559021s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.649151802062988s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.042074203491211s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.08662128448486328s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 726.8129229545593s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.8747131824493408s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.023328065872192383s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0008301734924316406s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 0.00010395050048828125s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 2.1457672119140625e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.0728836059570312e-05s
INFO | --- Analysis for roceeh-road took 866.0491597652435s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.6107139587402344s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006914138793945312s
Extra | Recovery of all triples for Thesaurus BNCF took 185.5794334411621s
Performance | Total latancy measurement for Thesaurus BNCF took 1.1266200542449951s
Amount of data | Number of triples check for Thesaurus BNCF took 1.1601228713989258s
Interoperability | New terms check for Thesaurus BNCF took 1.64686918258667s
Versatility | Languages check for Thesaurus BNCF took 9.435025453567505s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 1.6227562427520752s
Security | Check HTTPS for Thesaurus BNCF took 0.32579874992370605s
Interpretability | RDF structures check for Thesaurus BNCF took 0.5130414962768555s
Versatility | Serialization formats check for Thesaurus BNCF took 0.5529992580413818s
Availability | RDF dump link check for Thesaurus BNCF took 0.46562862396240234s
License | MR license check for Thesaurus BNCF took 0.3447988033294678s
License | HR license check for Thesaurus BNCF took 0.3444490432739258s
Amount of data | Number of property check for Thesaurus BNCF took 0.26452207565307617s
Understandability | Number of label check for Thesaurus BNCF took 0.4737420082092285s
Understandability | URI regex check for Thesaurus BNCF took 0.6754336357116699s
Understandability | Vocabs check for Thesaurus BNCF took 0.33583521842956543s
Verifiability | Authors check for Thesaurus BNCF took 0.32021284103393555s
Verifiability | Publishers check for Thesaurus BNCF took 0.1964712142944336s
Performance | Throughput check for Thesaurus BNCF took 11.404557704925537s
Amount of data | Check the number of entities for Thesaurus BNCF took 6.818771362304688e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.3848609924316406s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.4428420066833496s
Interlinking | skos check for Thesaurus BNCF took 0.5456380844116211s
Interlinking | skos check for Thesaurus BNCF took 0.44347214698791504s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.4452939033508301s
Currency | Creation date check for Thesaurus BNCF took 0.7493736743927002s
Currency | Modification date check for Thesaurus BNCF took 0.7245891094207764s
Rep.Conc. | URIs length for Thesaurus BNCF took 41.341214418411255s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.2835559844970703s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.29188084602355957s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.3458707332611084s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 20.8731529712677s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5042412281036377s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.143917560577393s
Consistency | Disjoint class check for Thesaurus BNCF took 0.6303896903991699s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.9098293781280518s
Consistency | Misplaced classes for Thesaurus BNCF took 7.571903467178345s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 13.608760833740234s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.6249425411224365s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.9853358268737793s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.560180187225342s
Security | Sign check for Thesaurus BNCF took 0.5312881469726562s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 24.064322233200073s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3506622314453125s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020249605178833008s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.486343383789062e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.3113021850585938e-05s
INFO | --- Analysis for bncf-ns took 388.0876259803772s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 2.7344276905059814s
Availability | VoID file availability check for COURAGE Dataset took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.2720792293548584s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.457069396972656e-05s
Believability | Calculation of trust value for COURAGE Dataset took 9.5367431640625e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 7.544764518737793s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2631494998931885s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.076957702636719e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for bll-thesaurus took 18.189682483673096s
Availability | SPARQL endpoint availability check for Inztrow took 0.00011277198791503906s
Availability | VoID file availability check for Inztrow took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2702357769012451s
Reputation | Calculation of the PageRank for Inztrow took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.147125244140625e-05s
Believability | Calculation of trust value for Inztrow took 1.0013580322265625e-05s
INFO | --- Analysis for Inztrow took 3.933800220489502s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.97905921936035s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.7089183330535889s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.02094268798828125s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.555152893066406e-05s
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 174.98110103607178s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.220008850097656e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.26756954193115234s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.24249267578125e-05s
Believability | Calculation of trust value for Temples of the Classical World took 7.3909759521484375e-06s
INFO | --- Analysis for classical_temples took 4.904510259628296s
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 3.7383475303649902s
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.0005862712860107422s
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.30793190002441406s
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.020969629287719727s
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.1682510375976562e-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.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.939338684082031e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 12.319628715515137s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.1205227375030518s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2611699104309082s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.250640869140625e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 11.119993448257446s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.1101558208465576s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2760002613067627s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.363059997558594e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-CRB took 12.983630895614624s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.1160709857940674s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.28096652030944824s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.298324584960938e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 10.60958981513977s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.1295151710510254s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2810852527618408s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.528594970703125e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.33514404296875e-05s
INFO | --- Analysis for ASCDC-DQOT took 12.06840467453003s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.1388912200927734s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.30134081840515137s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020640134811401367s
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.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.034706115722656e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 11.693753480911255s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.0848000049591064s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.00039958953857421875s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.2749001979827881s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.0207364559173584s
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.0019631385803222656s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 9.179115295410156e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 13.85154414176941s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.1219799518585205s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.2677741050720215s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020668983459472656s
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.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.650520324707031e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 10.609569072723389s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.143078327178955s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2653815746307373s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.7697296142578125e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 10.568079471588135s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.034453392028809s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2584569454193115s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.53131103515625e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.7220458984375e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 15.057862281799316s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.1522538661956787s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0004088878631591797s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.25133275985717773s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.748603820800781e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.059906005859375e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 10.144781589508057s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 2.1275644302368164s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.27841615676879883s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.058547973632812e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 10.63353157043457s
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.146045207977295s
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.00029158592224121094s
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.2704892158508301s
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.020819664001464844s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007309913635253906s
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.296966552734375e-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 8.344650268554688e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 11.645362138748169s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.143131732940674s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.24480319023132324s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.0205078125s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.649162292480469e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC_-_DNB took 10.089714765548706s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5406155586242676s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0007293224334716797s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.573806047439575s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.9789385795593262s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.4605445861816406s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.731461524963379s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 48.089208364486694s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.33272743225097656s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.22243571281433105s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5525445938110352s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3547091484069824s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.3853785991668701s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.4588336944580078s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 20.552729845046997s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.39381861686706543s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.8538722991943359s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.6636250019073486s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.3239603042602539s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.5538012981414795s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3854207992553711s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.39271593093872s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 8.702278137207031e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.35627293586730957s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3635883331298828s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.44942378997802734s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.32984209060668945s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.32298898696899414s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.8474986553192139s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.6764860153198242s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.3075077533721924s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.3340446949005127s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4947993755340576s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5141949653625488s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.4959332942962646s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.034667015075683594s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.02862858772277832s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.3988168239593506s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 2.66103196144104s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.4294419288635254s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.294736623764038s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.3233630657196045s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.5949511528015137s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.034857988357543945s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 1.5360918045043945s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.3841242790222168s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 10116.29001879692s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 1.5402064323425293s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.026291370391845703s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 6.771087646484375e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 9.5367431640625e-06s
INFO | --- Analysis for BVMC took 10359.555074930191s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.9631578922272s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.00039267539978027344s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.7422301769256592s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.021474123001098633s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007755756378173828s
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 8.821487426757812e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 800.0435245037079s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6552731990814209s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0003299713134765625s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.7516915798187256s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.021150588989257812s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for LucaniPharsalia took 5.611066102981567s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.46065783500671387s
Availability | VoID file availability check for Querolus in LiLa took 0.0013780593872070312s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.7788517475128174s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020661592483520508s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Querolus in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for Querolus took 4.733711004257202s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.4090251922607422s
Availability | VoID file availability check for UDante in LiLa took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.2605316638946533s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.02064204216003418s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for UDante took 4.3964385986328125s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 1.3589253425598145s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0003972053527832031s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 10.342793226242065s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 4.563319206237793s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.29751110076904297s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 2.773333787918091s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 59.336512088775635s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16637325286865234s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 1.2247719764709473s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.9763009548187256s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 1.2998089790344238s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24317455291748047s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 1.3216404914855957s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.8650360107421875s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 1.3072993755340576s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 1.101740837097168s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 1.0481643676757812s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.9952900409698486s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.9257659912109375s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 13.249159812927246s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.176399230957031e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.8310933113098145s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7779653072357178s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6218223571777344s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6549794673919678s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7511327266693115s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6603996753692627s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.8737170696258545s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.6907880306243896s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1726703643798828s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.318234920501709s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.7630171775817871s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 2.5024237632751465s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028704166412353516s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02844071388244629s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 1.0577964782714844s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.9325833320617676s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.058309316635132s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.2948083877563477s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 2.032672643661499s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03018927574157715s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 1.0072083473205566s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.167557954788208s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2289.2471055984497s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.0104467868804932s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.02540111541748047s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 2.9087066650390625e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0012013912200927734s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 3.0994415283203125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-05s
INFO | --- Analysis for ceo took 2457.0051007270813s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.463763952255249s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006320476531982422s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 106.64235186576843s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.5110650062561035s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6379764080047607s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.902616500854492s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.5439774990081787s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.6244635581970215s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.28443050384521484s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.27535009384155273s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 10.963657855987549s
License | MR license check for Cultural Heritage Thesaurus took 0.2784743309020996s
License | HR license check for Cultural Heritage Thesaurus took 0.3409607410430908s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.29972386360168457s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.34436678886413574s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5899710655212402s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.30796265602111816s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.2752556800842285s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.26599931716918945s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.818520069122314s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 3.4332275390625e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2674984931945801s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.2779114246368408s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.2844967842102051s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.2805023193359375s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.3226470947265625s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6010451316833496s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6119532585144043s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 34.03297209739685s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 4.1722822189331055s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.30423426628112793s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.29067134857177734s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.3119010925292969s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 6.30594277381897s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22234821319580078s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.2789621353149414s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.1214418411254883s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.3330113887786865s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 7.617563009262085s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.1511898040771484s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001499652862548828s
Security | Sign check for Cultural Heritage Thesaurus took 0.3054208755493164s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 308.2260363101959s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.9205598831176758s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 1.0734219551086426s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00010657310485839844s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 1.8499541282653809s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for cht took 536.1954982280731s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.9340896606445312s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2752077579498291s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.915496826171875e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.67572021484375e-06s
INFO | --- Analysis for greekchildrensartmuseum took 5.087212085723877s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.291534423828125e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2641603946685791s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.915496826171875e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.3909759521484375e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.4663259983062744s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.506082773208618s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.2816896438598633s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.021078109741210938s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.482269287109375e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 7.867813110351562e-06s
INFO | --- Analysis for ldt@library took 35.28578042984009s
Availability | SPARQL endpoint availability check for Muziekweb took 0.6778697967529297s
Availability | VoID file availability check for Muziekweb took 0.0005948543548583984s
Extra | Recovery of all triples for Muziekweb took 2.0110714435577393s
Performance | Total latancy measurement for Muziekweb took 1.4041354656219482s
Amount of data | Number of triples check for Muziekweb took 0.3748898506164551s
Interoperability | New terms check for Muziekweb took 1.7255573272705078s
Versatility | Languages check for Muziekweb took 53.418782472610474s
Interpretability | Number of blank nodes check for Muziekweb took 0.2786989212036133s
Interpretability | RDF structures check for Muziekweb took 0.6657252311706543s
Versatility | Serialization formats check for Muziekweb took 0.2856326103210449s
Availability | RDF dump link check for Muziekweb took 0.28716349601745605s
License | MR license check for Muziekweb took 0.3339247703552246s
License | HR license check for Muziekweb took 14.14398193359375s
Amount of data | Number of property check for Muziekweb took 0.2824978828430176s
Understandability | Number of label check for Muziekweb took 0.46854448318481445s
Understandability | URI regex check for Muziekweb took 0.7058894634246826s
Understandability | Vocabs check for Muziekweb took 0.25735044479370117s
Verifiability | Authors check for Muziekweb took 0.29286861419677734s
Verifiability | Publishers check for Muziekweb took 0.2732584476470947s
Performance | Throughput check for Muziekweb took 11.409978151321411s
Amount of data | Check the number of entities for Muziekweb took 8.249282836914062e-05s
Verifiability | Contribs. check for Muziekweb took 0.3078887462615967s
Interlinking | sameAs chians check for Muziekweb took 0.32354140281677246s
Interlinking | skos check for Muziekweb took 0.2807800769805908s
Interlinking | skos check for Muziekweb took 0.27039408683776855s
Timeliness | dataset update frequency check for Muziekweb took 0.30426788330078125s
Currency | Creation date check for Muziekweb took 0.7837448120117188s
Currency | Modification date check for Muziekweb took 0.7858676910400391s
Rep.Conc. | URIs length for Muziekweb took 1.8696770668029785s
Interoperability | New vocabularies check for Muziekweb took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.29616570472717285s
Accuracy | Check Functional Property for Muziekweb took 0.5031023025512695s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5044002532958984s
Accuracy | Check Empty annotation labels for Muziekweb took 2.6480319499969482s
Accuracy | Check White space in annotation for Muziekweb took 0.03467416763305664s
Accuracy | Check Datatype consistency for Muziekweb took 0.029728174209594727s
Consistency | Disjoint class check for Muziekweb took 0.4446077346801758s
Consistency | Check Misplaced properties for Muziekweb took 1.0941359996795654s
Consistency | Check Ontology hijacking for Muziekweb took 2.223581314086914s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.346803903579712s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.59867262840271s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03396892547607422s
Conciseness | Check Intensional conciseness for Muziekweb took 0.29172444343566895s
Security | Sign check for Muziekweb took 0.26259803771972656s
Availability | Check URIs Dereferenciability for Muziekweb took 1718.8932688236237s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.5119774341583252s
Reputation | Calculation of the PageRank for Muziekweb took 0.023670673370361328s
Interlinking | Calculation of Degree of Connection for Muziekweb took 7.200241088867188e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 7.963180541992188e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.6689300537109375e-06s
Believability | Calculation of trust value for Muziekweb took 5.9604644775390625e-06s
INFO | --- Analysis for muziekweb took 1847.960048675537s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 6.441370964050293s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.718510627746582s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 8.916854858398438e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 8.821487426757812e-06s
INFO | --- Analysis for nom took 27.87844181060791s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.7741913795471191s
Availability | VoID file availability check for Linked Stage Graph took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.26767587661743164s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 5.078315734863281e-05s
Believability | Calculation of trust value for Linked Stage Graph took 9.298324584960938e-06s
INFO | --- Analysis for slod took 3.7513651847839355s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 0.5422148704528809s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.2793149948120117s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02054905891418457s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.677078247070312e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for wasabi took 5.854107618331909s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2424604892730713s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.26102542877197266s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.020732641220092773s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.24249267578125e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.049041748046875e-05s
INFO | --- Analysis for wl-kg took 3.9073143005371094s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0007982254028320312s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.24831795692443848s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02041792869567871s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.316734313964844e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 7.62939453125e-06s
INFO | --- Analysis for yso took 6.294052839279175s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.5299530029296875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2684745788574219s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.0279159545898438e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 8.106231689453125e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.3194518089294434s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.363059997558594e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.25908684730529785s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 5.316734313964844e-05s
Believability | Calculation of trust value for Copyright Free Music took 7.3909759521484375e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.9082767963409424s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.649162292480469e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.25726795196533203s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.0279159545898438e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 7.62939453125e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.3423216342926025s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.410743713378906e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.25658726692199707s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02437901496887207s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.001165151596069336s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 4.553794860839844e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 9.059906005859375e-06s
INFO | --- Analysis for Sherry_Wine took 2.5851778984069824s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.291534423828125e-05s
Availability | VoID file availability check for Sherry Wine took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.23899054527282715s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020669937133789062s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.8133392333984375e-05s
Believability | Calculation of trust value for Sherry Wine took 7.62939453125e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.3251633644104004s
Availability | SPARQL endpoint availability check for Freeyork took 4.458427429199219e-05s
Availability | VoID file availability check for Freeyork took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2600092887878418s
Reputation | Calculation of the PageRank for Freeyork took 0.02055501937866211s
Interlinking | Calculation of Degree of Connection for Freeyork took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Freeyork took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.0001049041748046875s
Believability | Calculation of trust value for Freeyork took 7.3909759521484375e-06s
INFO | --- Analysis for freeyork-org took 2.9594531059265137s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.3392181396484375e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.26728224754333496s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.123283386230469e-05s
Believability | Calculation of trust value for Informatics Studies took 8.344650268554688e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.0372097492218018s
Availability | SPARQL endpoint availability check for MappingChange took 20.385430812835693s
Availability | VoID file availability check for MappingChange took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for MappingChange took 0.27918410301208496s
Reputation | Calculation of the PageRank for MappingChange took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for MappingChange took 1.52587890625e-05s
Interlinking | Calculation of Centrality for MappingChange took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for MappingChange took 1.3113021850585938e-05s
Believability | Calculation of trust value for MappingChange took 8.106231689453125e-06s
INFO | --- Analysis for mappingch took 53.3055305480957s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.3320033550262451s
Availability | VoID file availability check for Odeuropa Ontology took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.26763248443603516s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.2159347534179688e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 7.152557373046875e-06s
INFO | --- Analysis for Odeuropa took 3.1830949783325195s

--- Total time for analysis:240247.76302194595s ---
--- Total time for analysis:66.73548972831831 hours ---