Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 4.3392181396484375e-05s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.7305617332458496s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.6281955242156982s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.0004343986511230469s
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.4985573291778564s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 4.482269287109375e-05s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.7185666561126709s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.601478576660156e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 7.62939453125e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 3.799666166305542s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.458427429199219e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.23845744132995605s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.075599670410156e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 8.106231689453125e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 2.7743113040924072s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 4.410743713378906e-05s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.24192237854003906s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02092885971069336s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010251998901367188s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for abs-linked-data took 2.877654790878296s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 4.38690185546875e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.26111674308776855s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0006928443908691406s
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 7.62939453125e-06s
INFO | --- Analysis for academic-offer-of-unl took 2.8904011249542236s
Availability | SPARQL endpoint availability check for AcadOnto took 5.984306335449219e-05s
Availability | VoID file availability check for AcadOnto took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.24953699111938477s
Reputation | Calculation of the PageRank for AcadOnto took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.314018249511719e-05s
Believability | Calculation of trust value for AcadOnto took 8.344650268554688e-06s
INFO | --- Analysis for acadonto took 2.82316517829895s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.5299530029296875e-05s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.28035926818847656s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.886222839355469e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for acorn-sat took 2.8869717121124268s
Availability | SPARQL endpoint availability check for Addgene took 0.00012946128845214844s
Availability | VoID file availability check for Addgene took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Addgene took 0.29053306579589844s
Reputation | Calculation of the PageRank for Addgene took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for Addgene took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.600120544433594e-05s
Believability | Calculation of trust value for Addgene took 6.9141387939453125e-06s
INFO | --- Analysis for addgene took 2.936925172805786s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.458427429199219e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2518031597137451s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.107589721679688e-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 2.8344829082489014s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 4.315376281738281e-05s
Availability | VoID file availability check for AEMET metereological dataset took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.27535533905029297s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.267692565917969e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 6.9141387939453125e-06s
INFO | --- Analysis for aemet took 2.825716733932495s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.0531158447265625e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.26185154914855957s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.075599670410156e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 3.1948089599609375e-05s
INFO | --- Analysis for agenda-de-zaragoza took 2.883246421813965s
Availability | SPARQL endpoint availability check for AgriNepalData took 4.2438507080078125e-05s
Availability | VoID file availability check for AgriNepalData took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.250568151473999s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0006818771362304688s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.961822509765625e-05s
Believability | Calculation of trust value for AgriNepalData took 7.152557373046875e-06s
INFO | --- Analysis for agrinepaldata took 2.8334946632385254s
Availability | SPARQL endpoint availability check for AGRIS took 4.2438507080078125e-05s
Availability | VoID file availability check for AGRIS took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for AGRIS took 0.24880313873291016s
Reputation | Calculation of the PageRank for AGRIS took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for AGRIS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AGRIS took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.200241088867188e-05s
Believability | Calculation of trust value for AGRIS took 6.9141387939453125e-06s
INFO | --- Analysis for agris took 2.9101908206939697s
Availability | SPARQL endpoint availability check for AGROVOC took 4.57763671875e-05s
Availability | VoID file availability check for AGROVOC took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.2658722400665283s
Reputation | Calculation of the PageRank for AGROVOC took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.7697296142578125e-05s
Believability | Calculation of trust value for AGROVOC took 5.9604644775390625e-06s
INFO | --- Analysis for agrovoc-skos took 2.890630006790161s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.267692565917969e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.2745168209075928s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.600120544433594e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 1.1682510375976562e-05s
INFO | --- Analysis for aksworg took 2.793449640274048s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.553794860839844e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.24737286567687988s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.9325485229492188e-05s
Believability | Calculation of trust value for AlchemyAPI took 1.2159347534179688e-05s
INFO | --- Analysis for alchemyapi took 2.732038736343384s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.172325134277344e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.2560536861419678s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.24249267578125e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 8.106231689453125e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.8403849601745605s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.1631712913513184s
Availability | VoID file availability check for aliada-scanbit-net took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.2501251697540283s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.000110626220703125s
Believability | Calculation of trust value for aliada-scanbit-net took 6.67572021484375e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.044731378555298s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.220008850097656e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.2592654228210449s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.123283386230469e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 5.4836273193359375e-06s
INFO | --- Analysis for allen-brain-atlas took 2.8663668632507324s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 4.315376281738281e-05s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.26244473457336426s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 6.651878356933594e-05s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 6.4373016357421875e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 2.9140372276306152s
Availability | SPARQL endpoint availability check for Alojamientos took 4.1961669921875e-05s
Availability | VoID file availability check for Alojamientos took 0.0003292560577392578s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.2719395160675049s
Reputation | Calculation of the PageRank for Alojamientos took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 2.9802322387695312e-05s
Believability | Calculation of trust value for Alojamientos took 6.9141387939453125e-06s
INFO | --- Analysis for alojamientos-zaragoza took 2.8445003032684326s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 4.3392181396484375e-05s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.26712822914123535s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020178794860839844s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.62396240234375e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 6.4373016357421875e-06s
INFO | --- Analysis for alpino-rdf took 2.8341782093048096s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.38690185546875e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.25694870948791504s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 2.956390380859375e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 6.198883056640625e-06s
INFO | --- Analysis for am-collections-online took 2.763019323348999s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.24873685836791992s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for amon took 2.9355618953704834s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7619304656982422s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.23922371864318848s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 8.463859558105469e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.049041748046875e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.6390671730041504s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 5.507469177246094e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.24910235404968262s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 2.9325485229492188e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 5.9604644775390625e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.8388209342956543s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.267692565917969e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.2450108528137207s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.075599670410156e-05s
Believability | Calculation of trust value for Animal Diversity Web took 6.67572021484375e-06s
INFO | --- Analysis for animal-diversity-web took 2.8439080715179443s
Availability | SPARQL endpoint availability check for apache took 4.839897155761719e-05s
Availability | VoID file availability check for apache took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for apache took 0.23938727378845215s
Reputation | Calculation of the PageRank for apache took 0.02019643783569336s
Interlinking | Calculation of Degree of Connection for apache took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for apache took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for apache took 5.4836273193359375e-05s
Believability | Calculation of trust value for apache took 7.867813110351562e-06s
INFO | --- Analysis for apache took 2.837848663330078s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.25115013122558594s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf took 2.857156753540039s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.26872849464416504s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.839897155761719e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 2.8566713333129883s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.25019335746765137s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 2.827575206756592s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.2595858573913574s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-en-es took 2.833078145980835s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.2510967254638672s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02045893669128418s
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.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 2.8118467330932617s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.24464178085327148s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 2.8079426288604736s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.2609374523162842s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 2.858814239501953s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 6.67572021484375e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0003757476806640625s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.23949003219604492s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.02081012725830078s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 2.8410117626190186s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 6.651878356933594e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2669258117675781s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 2.8448994159698486s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 7.534027099609375e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2541036605834961s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02099752426147461s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-an took 2.8164408206939697s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 5.7697296142578125e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.26666808128356934s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.021071672439575195s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.9591064453125e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 2.856067419052124s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.26212453842163086s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 2.8437106609344482s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.24350929260253906s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020660400390625s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 2.7753665447235107s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.25174760818481445s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 2.787436008453369s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.23998355865478516s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 2.756727457046509s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.23812246322631836s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 2.833902597427368s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 5.078315734863281e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.24067330360412598s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 2.8074491024017334s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.24501943588256836s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 2.7799456119537354s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.25037050247192383s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 2.836505651473999s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2566211223602295s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 2.8382210731506348s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.23550820350646973s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 2.8197648525238037s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 5.078315734863281e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2420792579650879s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0008831024169921875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 2.7657604217529297s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.00030422210693359375s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2849905490875244s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 2.787719249725342s
Availability | SPARQL endpoint availability check for AragoDBPedia took 6.723403930664062e-05s
Availability | VoID file availability check for AragoDBPedia took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 0.2609367370605469s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.020210981369018555s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 3.528594970703125e-05s
Believability | Calculation of trust value for AragoDBPedia took 6.67572021484375e-06s
INFO | --- Analysis for aragodbpedia took 2.7411375045776367s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 4.124641418457031e-05s
Availability | VoID file availability check for Archives Hub Linked Data took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2393200397491455s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.315376281738281e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for archiveshub-linkeddata took 2.779951810836792s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.267692565917969e-05s
Availability | VoID file availability check for Archivi ISMA took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.24590730667114258s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 2.86102294921875e-05s
Believability | Calculation of trust value for Archivi ISMA took 6.67572021484375e-06s
INFO | --- Analysis for archivio-isma took 2.7979862689971924s
Availability | SPARQL endpoint availability check for ARIADNE took 4.3392181396484375e-05s
Availability | VoID file availability check for ARIADNE took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.22784972190856934s
Reputation | Calculation of the PageRank for ARIADNE took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for ARIADNE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ARIADNE took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 2.7418136596679688e-05s
Believability | Calculation of trust value for ARIADNE took 6.9141387939453125e-06s
INFO | --- Analysis for ariadne took 2.7159194946289062s
Availability | SPARQL endpoint availability check for Aristotle University took 4.673004150390625e-05s
Availability | VoID file availability check for Aristotle University took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.2804543972015381s
Reputation | Calculation of the PageRank for Aristotle University took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for Aristotle University took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 2.7179718017578125e-05s
Believability | Calculation of trust value for Aristotle University took 7.152557373046875e-06s
INFO | --- Analysis for aristotle-university took 2.730323553085327s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.315376281738281e-05s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.25867533683776855s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 2.7894973754882812e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 6.4373016357421875e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 2.79292368888855s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.291534423828125e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.2662651538848877s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0201871395111084s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 2.765655517578125e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 8.106231689453125e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.7455992698669434s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.267692565917969e-05s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.24888229370117188s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.7670135498046875e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0013580322265625e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 2.729458808898926s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.23204541206359863s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.632110595703125e-05s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 2.833223342895508s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.935264587402344e-05s
Availability | VoID file availability check for Arthroscopy community took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2661716938018799s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 9.655952453613281e-05s
Believability | Calculation of trust value for Arthroscopy community took 6.4373016357421875e-06s
INFO | --- Analysis for arthroscopy took 2.87272047996521s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.291534423828125e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.24485087394714355s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.222724914550781e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.2159347534179688e-05s
INFO | --- Analysis for asit took 2.8454723358154297s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.267692565917969e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.23997712135314941s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.02021503448486328s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.647804260253906e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 7.3909759521484375e-06s
INFO | --- Analysis for asjp took 2.8110005855560303s
Availability | SPARQL endpoint availability check for ASN:US took 5.412101745605469e-05s
Availability | VoID file availability check for ASN:US took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2643890380859375s
Reputation | Calculation of the PageRank for ASN:US took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.651878356933594e-05s
Believability | Calculation of trust value for ASN:US took 6.9141387939453125e-06s
INFO | --- Analysis for asn-us took 2.8673465251922607s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.1961669921875e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.2532670497894287s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.7894973754882812e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 1.1920928955078125e-05s
INFO | --- Analysis for aspire-mmu took 2.798891305923462s
Availability | SPARQL endpoint availability check for associations took 4.363059997558594e-05s
Availability | VoID file availability check for associations took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for associations took 0.2563507556915283s
Reputation | Calculation of the PageRank for associations took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for associations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for associations took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for associations took 6.198883056640625e-05s
Believability | Calculation of trust value for associations took 6.67572021484375e-06s
INFO | --- Analysis for associations took 2.8753395080566406s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.38690185546875e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2597641944885254s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.765655517578125e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 7.3909759521484375e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.8738770484924316s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.3392181396484375e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.2663609981536865s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.606910705566406e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 7.152557373046875e-06s
INFO | --- Analysis for athelia-rfid took 2.835439443588257s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.291534423828125e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2544698715209961s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.6941299438476562e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.801025152206421s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 4.220008850097656e-05s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.25494933128356934s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0008175373077392578s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.036064147949219e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 9.5367431640625e-06s
INFO | --- Analysis for austrian_ski_racers took 2.745210886001587s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 30.253188371658325s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2897517681121826s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.936622619628906e-05s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.0067901611328125e-06s
INFO | --- Analysis for b3kat took 63.147116899490356s
Availability | SPARQL endpoint availability check for BabelNet took 4.506111145019531e-05s
Availability | VoID file availability check for BabelNet took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for BabelNet took 0.2685680389404297s
Reputation | Calculation of the PageRank for BabelNet took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00015997886657714844s
Believability | Calculation of trust value for BabelNet took 7.62939453125e-06s
INFO | --- Analysis for babelnet took 2.8314149379730225s
Availability | SPARQL endpoint availability check for BAMS took 4.267692565917969e-05s
Availability | VoID file availability check for BAMS took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for BAMS took 0.2688612937927246s
Reputation | Calculation of the PageRank for BAMS took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for BAMS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for BAMS took 2.7894973754882812e-05s
Believability | Calculation of trust value for BAMS took 6.9141387939453125e-06s
INFO | --- Analysis for bams took 2.787656545639038s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 5.1975250244140625e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.253368616104126s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.2159347534179688e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 2.7582507133483887s
Availability | SPARQL endpoint availability check for BBC Music took 0.6199784278869629s
Availability | VoID file availability check for BBC Music took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for BBC Music took 0.2769749164581299s
Reputation | Calculation of the PageRank for BBC Music took 0.02031111717224121s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012063980102539062s
Believability | Calculation of trust value for BBC Music took 7.152557373046875e-06s
INFO | --- Analysis for bbc-music took 3.4904415607452393s
Availability | SPARQL endpoint availability check for BBC Programmes took 4.1961669921875e-05s
Availability | VoID file availability check for BBC Programmes took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2565586566925049s
Reputation | Calculation of the PageRank for BBC Programmes took 0.02137017250061035s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010085105895996094s
Believability | Calculation of trust value for BBC Programmes took 7.3909759521484375e-06s
INFO | --- Analysis for bbc-programmes took 2.8686418533325195s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.4988400936126709s
Availability | VoID file availability check for BBC Wildlife Finder took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2581145763397217s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 9.441375732421875e-05s
Believability | Calculation of trust value for BBC Wildlife Finder took 6.198883056640625e-06s
INFO | --- Analysis for bbc-wildlife-finder took 3.3379862308502197s
Availability | SPARQL endpoint availability check for BBOP took 4.315376281738281e-05s
Availability | VoID file availability check for BBOP took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for BBOP took 0.2650034427642822s
Reputation | Calculation of the PageRank for BBOP took 0.020286083221435547s
Interlinking | Calculation of Degree of Connection for BBOP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for BBOP took 4.5299530029296875e-05s
Believability | Calculation of trust value for BBOP took 7.152557373046875e-06s
INFO | --- Analysis for bbop took 2.8448450565338135s
Availability | SPARQL endpoint availability check for BBOP took 9.226799011230469e-05s
Availability | VoID file availability check for BBOP took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for BBOP took 0.25876951217651367s
Reputation | Calculation of the PageRank for BBOP took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for BBOP took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.6702880859375e-05s
Believability | Calculation of trust value for BBOP took 6.9141387939453125e-06s
INFO | --- Analysis for bbop-selected took 2.98008394241333s
Availability | SPARQL endpoint availability check for Bdgp took 4.315376281738281e-05s
Availability | VoID file availability check for Bdgp took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2504007816314697s
Reputation | Calculation of the PageRank for Bdgp took 0.020236968994140625s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Bdgp took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bdgp took 7.3909759521484375e-06s
INFO | --- Analysis for bdgp took 2.844085216522217s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.9114227294921875e-05s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.26120901107788086s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02065277099609375s
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.000701904296875s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.29425048828125e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 7.152557373046875e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 2.774059295654297s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.2438507080078125e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.2564873695373535s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.0040740966796875e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 7.152557373046875e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.784525156021118s
Availability | SPARQL endpoint availability check for berlios took 4.291534423828125e-05s
Availability | VoID file availability check for berlios took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for berlios took 0.2480924129486084s
Reputation | Calculation of the PageRank for berlios took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for berlios took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for berlios took 8.535385131835938e-05s
Believability | Calculation of trust value for berlios took 2.2172927856445312e-05s
INFO | --- Analysis for berlios took 2.8074452877044678s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 4.291534423828125e-05s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.27129673957824707s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 3.123283386230469e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0008738040924072266s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.34600830078125e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for bfs-linked-data took 2.8301584720611572s
Availability | SPARQL endpoint availability check for BibBase took 4.744529724121094e-05s
Availability | VoID file availability check for BibBase took 0.0003535747528076172s
Completeness | Calculation of interlinking completeness for BibBase took 0.24867773056030273s
Reputation | Calculation of the PageRank for BibBase took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for BibBase took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.322166442871094e-05s
Believability | Calculation of trust value for BibBase took 6.9141387939453125e-06s
INFO | --- Analysis for bibbase took 2.828169822692871s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.267692565917969e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.24049615859985352s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.274482727050781e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 2.8129541873931885s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.363059997558594e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.25702452659606934s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010085105895996094s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 6.4373016357421875e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 2.89521861076355s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.220008850097656e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.24201560020446777s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 2.765655517578125e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.7837917804718018s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.1484832763671875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.26683878898620605s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020600557327270508s
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.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.86102294921875e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 6.9141387939453125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 2.7752585411071777s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.26988983154296875s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.8371810913085938e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 6.9141387939453125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.751086711883545s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.2694063186645508s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.779979944229126s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.2395915985107422s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0008630752563476562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.608268737792969e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 2.8232243061065674s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.2360239028930664s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00010800361633300781s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-biomodels took 2.6894044876098633s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.26517295837402344s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.00086212158203125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.361701965332031e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 2.9099395275115967s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.25809216499328613s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.021915435791015625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004048347473144531s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-bioportal took 2.819342613220215s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 7.152557373046875e-05s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.2544081211090088s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.054473876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-chembl took 2.842240333557129s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.27483582496643066s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.291534423828125e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 2.876488208770752s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.2897799015045166s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.127357482910156e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-ctd took 2.9225480556488037s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.315376281738281e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.2661736011505127s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.649162292480469e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-dataset took 2.8701982498168945s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 4.458427429199219e-05s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.2574343681335449s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020398855209350586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.031990051269531e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 2.8152620792388916s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 4.458427429199219e-05s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.264484167098999s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 9.822845458984375e-05s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-drugbank took 2.8131561279296875s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 7.796287536621094e-05s
Availability | VoID file availability check for Bio2RDF::Genage took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.27391862869262695s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.7220458984375e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-genage took 2.8527886867523193s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.482269287109375e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.2541382312774658s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.650520324707031e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-genbank took 2.7899844646453857s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0003170967102050781s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.2767183780670166s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 4.649162292480469e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-gendr took 2.848863363265991s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.26586031913757324s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.507469177246094e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-goa took 2.846898317337036s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.2558608055114746s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.000102996826171875s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-hgnc took 2.8420071601867676s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 7.748603820800781e-05s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.00030040740966796875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.2312464714050293s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 4.76837158203125e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-homologene took 2.84063458442688s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.2453014850616455s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 2.8133392333984375e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-inoh took 2.7581799030303955s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.2389850616455078s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 9.393692016601562e-05s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-interpro took 2.7770678997039795s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.2508094310760498s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020282983779907227s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.128715515136719e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-iproclass took 2.8068954944610596s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 4.458427429199219e-05s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.2583956718444824s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02013993263244629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.653236389160156e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-irefindex took 2.8457090854644775s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.258991003036499s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020910024642944336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.127357482910156e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-kegg took 2.8698995113372803s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.2684140205383301s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 2.8032431602478027s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 4.38690185546875e-05s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2534794807434082s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020660400390625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 2.86102294921875e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 2.847503185272217s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 4.3392181396484375e-05s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.2650432586669922s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.100799560546875e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-lsr took 2.834226131439209s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 4.839897155761719e-05s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.25459909439086914s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020615577697753906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 6.890296936035156e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-mesh took 2.7967302799224854s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.2660250663757324s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.00010418891906738281s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-mgi took 2.8538382053375244s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.25995469093322754s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.000110626220703125s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 2.781371831893921s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.2780749797821045s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020208120346069336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.1484832763671875e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-ndc took 2.857771635055542s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.76837158203125e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.2775261402130127s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 2.7894973754882812e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-netpath took 2.7948780059814453s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.24344539642333984s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 2.7894973754882812e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-nextprot took 2.8308844566345215s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::Omim took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.2572205066680908s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00014066696166992188s
Believability | Calculation of trust value for Bio2RDF::Omim took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-omim took 2.751080274581909s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.172325134277344e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0008089542388916016s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.26257967948913574s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020338773727416992s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.743171691894531e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 2.792349338531494s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.2580454349517822s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 6.818771362304688e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-orphanet took 2.7382521629333496s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 7.963180541992188e-05s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.2908337116241455s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020647287368774414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.4332275390625e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 2.8897736072540283s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 4.38690185546875e-05s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.2849891185760498s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.05718994140625e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 2.859433174133301s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.3392181396484375e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2476053237915039s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.02877354621887207s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 2.896841287612915s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.2824275493621826s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pid took 2.8725173473358154s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.2795841693878174s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020323991775512695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 2.8895373344421387s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 4.887580871582031e-05s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.27910804748535156s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013017654418945312s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-pubmed took 2.8731765747070312s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 5.1021575927734375e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.2576310634613037s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 8.058547973632812e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-reactome took 2.8344290256500244s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.2482292652130127s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.125999450683594e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-rhea took 2.8970718383789062s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0003116130828857422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.2415933609008789s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.319450378417969e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-sabiork took 2.734865188598633s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0003554821014404297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.27449488639831543s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010371208190917969s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-sgd took 2.8938376903533936s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 6.508827209472656e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.27985191345214844s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0009436607360839844s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.8623809814453125e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 2.8280344009399414s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::Sider took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.2739596366882324s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.910064697265625e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-sider took 2.8606414794921875s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 5.650520324707031e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.27962708473205566s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-spike took 2.85809588432312s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.5299530029296875e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.24904823303222656s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 3.838539123535156e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-taxon took 2.8389177322387695s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 7.081031799316406e-05s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.2890944480895996s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.0001125335693359375s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 2.8330206871032715s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.24335956573486328s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 2.813401699066162s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 5.1975250244140625e-05s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.2844235897064209s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.557868957519531e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-wormbase took 2.8042595386505127s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 4.172325134277344e-05s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.248793363571167s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020409584045410156s
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.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 0.00010085105895996094s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 6.9141387939453125e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 2.854389190673828s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.26102137565612793s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.021526336669921875s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0010077953338623047s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.029273986816406e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for biolit took 2.805230140686035s
Availability | SPARQL endpoint availability check for BioModels RDF took 4.410743713378906e-05s
Availability | VoID file availability check for BioModels RDF took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.24872064590454102s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.743171691894531e-05s
Believability | Calculation of trust value for BioModels RDF took 7.867813110351562e-06s
INFO | --- Analysis for biomodels-rdf took 2.87158203125s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 9.202957153320312e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.24945807456970215s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.021334409713745117s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0011906623840332031s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0008087158203125s
Believability | Calculation of trust value for Amphibian gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-aao took 2.794456958770752s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.172325134277344e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.29068541526794434s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002942085266113281s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-aba took 2.8116464614868164s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.26658177375793457s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015263557434082031s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-acgt took 2.9676859378814697s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.2438507080078125e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.26108336448669434s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.000324249267578125s
Believability | Calculation of trust value for Animal natural history and life history took 7.62939453125e-06s
INFO | --- Analysis for bioportal-adw took 2.8574793338775635s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 7.62939453125e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.26195740699768066s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00046563148498535156s
Believability | Calculation of trust value for Anatomical Entity Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-aeo took 2.7982311248779297s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.27228713035583496s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.021631479263305664s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009961128234863281s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-aero took 2.808708429336548s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.267692565917969e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2451343536376953s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.02089977264404297s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004076957702636719s
Believability | Calculation of trust value for AI/RHEUM took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-air took 2.859602212905884s
Availability | SPARQL endpoint availability check for Amino Acid took 4.9591064453125e-05s
Availability | VoID file availability check for Amino Acid took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.24994754791259766s
Reputation | Calculation of the PageRank for Amino Acid took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00026345252990722656s
Believability | Calculation of trust value for Amino Acid took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-amino-acid took 2.8719236850738525s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2548339366912842s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002923011779785156s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-apo took 2.879559278488159s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.2438507080078125e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2753567695617676s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0002498626708984375s
Believability | Calculation of trust value for African Traditional Medicine took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-atmo took 2.918699026107788s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.25096750259399414s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020879268646240234s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.036064147949219e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ato took 2.858185291290283s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2674579620361328s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020287275314331055s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013413429260253906s
Believability | Calculation of trust value for BioAssay Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-bao took 2.7905800342559814s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2574176788330078s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020897865295410156s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00041103363037109375s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.7962725162506104s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2413649559020996s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020349979400634766s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003216266632080078s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-bcgo took 2.8231728076934814s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.25541043281555176s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020792484283447266s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014247894287109375s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-bdo took 2.7610106468200684s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.26502299308776855s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.02021956443786621s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005011558532714844s
Believability | Calculation of trust value for Basic Formal Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-bfo took 2.8235490322113037s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.220008850097656e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.279909610748291s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007598400115966797s
Believability | Calculation of trust value for Bleeding History Phenotype took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-bho took 2.893467903137207s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.27971506118774414s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020856380462646484s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00044536590576171875s
Believability | Calculation of trust value for Bilateria anatomy took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-bila took 2.8643438816070557s
Availability | SPARQL endpoint availability check for BIRNLex took 4.1484832763671875e-05s
Availability | VoID file availability check for BIRNLex took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.26973557472229004s
Reputation | Calculation of the PageRank for BIRNLex took 0.020348310470581055s
Interlinking | Calculation of Degree of Connection for BIRNLex took 3.075599670410156e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014770030975341797s
Believability | Calculation of trust value for BIRNLex took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-birnlex took 3.002847194671631s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2693796157836914s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0008587837219238281s
Believability | Calculation of trust value for Gene Regulation Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.8642561435699463s
Availability | SPARQL endpoint availability check for BioPAX took 6.723403930664062e-05s
Availability | VoID file availability check for BioPAX took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2673647403717041s
Reputation | Calculation of the PageRank for BioPAX took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for BioPAX took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.34600830078125e-05s
Believability | Calculation of trust value for BioPAX took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-bp took 2.823033094406128s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2650771141052246s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003476142883300781s
Believability | Calculation of trust value for Biomedical Resource Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.800050973892212s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Spatial Ontology took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.25084900856018066s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02081751823425293s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00023794174194335938s
Believability | Calculation of trust value for Spatial Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bspo took 2.8046138286590576s
Availability | SPARQL endpoint availability check for BioTop took 4.792213439941406e-05s
Availability | VoID file availability check for BioTop took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for BioTop took 0.24560260772705078s
Reputation | Calculation of the PageRank for BioTop took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for BioTop took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006663799285888672s
Believability | Calculation of trust value for BioTop took 7.62939453125e-06s
INFO | --- Analysis for bioportal-bt took 2.8243274688720703s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 7.224082946777344e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.2510488033294678s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020887374877929688s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0009076595306396484s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-bto took 2.804725170135498s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.2677030563354492s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02070450782775879s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.001970529556274414s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-canco took 2.8753421306610107s
Availability | SPARQL endpoint availability check for CAO took 4.291534423828125e-05s
Availability | VoID file availability check for CAO took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for CAO took 0.2626833915710449s
Reputation | Calculation of the PageRank for CAO took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for CAO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006053447723388672s
Believability | Calculation of trust value for CAO took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cao took 2.940904140472412s
Availability | SPARQL endpoint availability check for CareLex took 4.172325134277344e-05s
Availability | VoID file availability check for CareLex took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for CareLex took 0.2567710876464844s
Reputation | Calculation of the PageRank for CareLex took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for CareLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.9591064453125e-05s
Believability | Calculation of trust value for CareLex took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-carelex took 2.8958611488342285s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2791101932525635s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007991790771484375s
Believability | Calculation of trust value for Cell Cycle Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-cco took 2.8607847690582275s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 5.555152893066406e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.26282596588134766s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002512931823730469s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cdao took 2.8492350578308105s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.220008850097656e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2890641689300537s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008294582366943359s
Believability | Calculation of trust value for Chemical entities of biological interest took 7.62939453125e-06s
INFO | --- Analysis for bioportal-chebi took 2.833514451980591s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.4345855712890625e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.2697608470916748s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00026035308837890625s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.944343090057373s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.24697089195251465s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007495880126953125s
Believability | Calculation of trust value for Chemical Information Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-cheminf took 2.8563592433929443s
Availability | SPARQL endpoint availability check for Cell type took 4.9591064453125e-05s
Availability | VoID file availability check for Cell type took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Cell type took 0.27455997467041016s
Reputation | Calculation of the PageRank for Cell type took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for Cell type took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.000377655029296875s
Believability | Calculation of trust value for Cell type took 7.62939453125e-06s
INFO | --- Analysis for bioportal-cl took 2.838465690612793s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 5.53131103515625e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.2594614028930664s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008008480072021484s
Believability | Calculation of trust value for Cell Line Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-clo took 2.943187952041626s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2734031677246094s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017380714416503906s
Believability | Calculation of trust value for Clinical Measurement Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-cmo took 2.7218635082244873s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.24333882331848145s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02012801170349121s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00020265579223632812s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-cno took 2.886181116104126s
Availability | SPARQL endpoint availability check for Wheat trait took 4.1484832763671875e-05s
Availability | VoID file availability check for Wheat trait took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.25873231887817383s
Reputation | Calculation of the PageRank for Wheat trait took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.00087738037109375s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 6.103515625e-05s
Believability | Calculation of trust value for Wheat trait took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.838578462600708s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.267692565917969e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.00032019615173339844s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.25725650787353516s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00033926963806152344s
Believability | Calculation of trust value for Cognitive Atlas took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-cogat took 2.8094913959503174s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0003376007080078125s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2608602046966553s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020902395248413086s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0011169910430908203s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0009560585021972656s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cogpo took 2.7995378971099854s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.2438507080078125e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.26488447189331055s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004134178161621094s
Believability | Calculation of trust value for Current Procedural Terminology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-cpt took 2.801124334335327s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.124641418457031e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.2571675777435303s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020195960998535156s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017538070678710938s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-csp took 2.78044056892395s
Availability | SPARQL endpoint availability check for COSTART took 4.220008850097656e-05s
Availability | VoID file availability check for COSTART took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for COSTART took 0.24346160888671875s
Reputation | Calculation of the PageRank for COSTART took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009856224060058594s
Believability | Calculation of trust value for COSTART took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-cst took 2.8851842880249023s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.1484832763671875e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.24665117263793945s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 2.9802322387695312e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005033016204833984s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ctcae took 2.8290393352508545s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.1961669921875e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2635035514831543s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020274639129638672s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00043845176696777344s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ctx took 2.870974063873291s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.2438507080078125e-05s
Availability | VoID file availability check for Dendritic cell took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.25348758697509766s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020605802536010742s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00030422210693359375s
Believability | Calculation of trust value for Dendritic cell took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.86838960647583s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.25598883628845215s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.107589721679688e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ddanat took 2.819859027862549s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.1484832763671875e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.26006340980529785s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009567737579345703s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ddi took 2.82686448097229s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 7.486343383789062e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2656574249267578s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.320808410644531e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.8765485286712646s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.27538323402404785s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020895719528198242s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0008955001831054688s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00020432472229003906s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.839115858078003s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Human disease ontology took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2555990219116211s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006403923034667969s
Believability | Calculation of trust value for Human disease ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-doid took 2.817007303237915s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2408151626586914s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008065700531005859s
Believability | Calculation of trust value for Electrocardiography Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ecg took 2.8568029403686523s
Availability | SPARQL endpoint availability check for Evidence codes took 4.2438507080078125e-05s
Availability | VoID file availability check for Evidence codes took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.260953426361084s
Reputation | Calculation of the PageRank for Evidence codes took 0.020392894744873047s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 2.7418136596679688e-05s
Believability | Calculation of trust value for Evidence codes took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-eco took 2.7286641597747803s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.2543947696685791s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0009644031524658203s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0018994808197021484s
Believability | Calculation of trust value for Experimental Factor Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-efo took 2.8815577030181885s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.220008850097656e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.24848532676696777s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011792182922363281s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ehda took 2.853379964828491s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.267692565917969e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.26508283615112305s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007357597351074219s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.8401784896850586s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.220008850097656e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.26215410232543945s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.02088332176208496s
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.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005633831024169922s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.898643970489502s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.124641418457031e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.28323936462402344s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.9087066650390625e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-emap took 2.9346110820770264s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Environment Ontology took 0.000782012939453125s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2625923156738281s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0009233951568603516s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0005028247833251953s
Believability | Calculation of trust value for Environment Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-envo took 2.9175121784210205s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.1484832763671875e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2463219165802002s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0002918243408203125s
Believability | Calculation of trust value for Plant environmental conditions took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-eo took 2.7893548011779785s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.2646923065185547s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0013070106506347656s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ep took 2.9083657264709473s
Availability | SPARQL endpoint availability check for Epilepsy took 4.291534423828125e-05s
Availability | VoID file availability check for Epilepsy took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2560160160064697s
Reputation | Calculation of the PageRank for Epilepsy took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for Epilepsy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Epilepsy took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001239776611328125s
Believability | Calculation of trust value for Epilepsy took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.867215633392334s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.220008850097656e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.23880743980407715s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020648717880249023s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0012159347534179688s
Believability | Calculation of trust value for eagle-i research resource ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ero took 2.8556861877441406s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.458427429199219e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.25974249839782715s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011355876922607422s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-ev took 2.8110997676849365s
Availability | SPARQL endpoint availability check for ExO took 4.1961669921875e-05s
Availability | VoID file availability check for ExO took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for ExO took 0.28624653816223145s
Reputation | Calculation of the PageRank for ExO took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for ExO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00024247169494628906s
Believability | Calculation of trust value for ExO took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-exo took 2.8448407649993896s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 5.555152893066406e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.255995512008667s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.000110626220703125s
Believability | Calculation of trust value for Fungal gross anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-fao took 2.842378616333008s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.172325134277344e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.26669764518737793s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00019049644470214844s
Believability | Calculation of trust value for Biological imaging methods took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-fbbi took 2.8415236473083496s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.38690185546875e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.24814915657043457s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006725788116455078s
Believability | Calculation of trust value for Drosophila gross anatomy took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-fbbt took 2.85787296295166s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.267692565917969e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2379169464111328s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004265308380126953s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-fbcv took 2.7845358848571777s
Availability | SPARQL endpoint availability check for Drosophila development took 4.267692565917969e-05s
Availability | VoID file availability check for Drosophila development took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2603425979614258s
Reputation | Calculation of the PageRank for Drosophila development took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.506111145019531e-05s
Believability | Calculation of trust value for Drosophila development took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-fbdv took 2.864027261734009s
Availability | SPARQL endpoint availability check for Fly taxonomy took 5.793571472167969e-05s
Availability | VoID file availability check for Fly taxonomy took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2608461380004883s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.000362396240234375s
Believability | Calculation of trust value for Fly taxonomy took 7.62939453125e-06s
INFO | --- Analysis for bioportal-fbsp took 2.8571765422821045s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.267692565917969e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.26207804679870605s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002193450927734375s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.7787108421325684s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.26343345642089844s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.02112436294555664s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0009975433349609375s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0005092620849609375s
Believability | Calculation of trust value for Family Health History Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-fhho took 2.883958339691162s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.24953866004943848s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.021985530853271484s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010437965393066406s
Believability | Calculation of trust value for Influenza Ontology took 1.9550323486328125e-05s
INFO | --- Analysis for bioportal-flu took 2.8693363666534424s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.00036835670471191406s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.23717904090881348s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 7.653236389160156e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-fma took 2.8871569633483887s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.26125454902648926s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00013375282287597656s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-fypo took 2.815426826477051s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 5.793571472167969e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.24928045272827148s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.131431579589844e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-geospecies took 2.785001277923584s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.25528550148010254s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016379356384277344s
Believability | Calculation of trust value for General Formal Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-gfo took 2.8375186920166016s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.363059997558594e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2471146583557129s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006186962127685547s
Believability | Calculation of trust value for General Formal Ontology: Biology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-gfo-bio took 2.8153750896453857s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 5.5789947509765625e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2541465759277344s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.02104949951171875s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0009000301361083984s
Believability | Calculation of trust value for Gene Ontology Extension took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.8382325172424316s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Gene Ontology took 0.00031113624572753906s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.25005555152893066s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008537769317626953s
Believability | Calculation of trust value for Gene Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.837376594543457s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.267692565917969e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.2649238109588623s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.075599670410156e-05s
Believability | Calculation of trust value for Cereal Plant Development took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-gro took 2.812852382659912s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2397000789642334s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004513263702392578s
Believability | Calculation of trust value for Cereal plant gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.821868419647217s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.27497100830078125s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0008378028869628906s
Believability | Calculation of trust value for Gene Regulation Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.826103448867798s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2562541961669922s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0006067752838134766s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-hao took 2.9829163551330566s
Availability | SPARQL endpoint availability check for HCPCS took 4.3392181396484375e-05s
Availability | VoID file availability check for HCPCS took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2659177780151367s
Reputation | Calculation of the PageRank for HCPCS took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002276897430419922s
Believability | Calculation of trust value for HCPCS took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.8654656410217285s
Availability | SPARQL endpoint availability check for Health Level Seven took 5.435943603515625e-05s
Availability | VoID file availability check for Health Level Seven took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.27573323249816895s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012850761413574219s
Believability | Calculation of trust value for Health Level Seven took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-hl7 took 2.853038787841797s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.363059997558594e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.264324426651001s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020998477935791016s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003561973571777344s
Believability | Calculation of trust value for HEALTH_INDICATORS took 7.62939453125e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.8796908855438232s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.24471306800842285s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.0279159545898438e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-hom took 2.8920207023620605s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 7.557868957519531e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2759897708892822s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020998716354370117s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.218650817871094e-05s
Believability | Calculation of trust value for HOM-HARVARD took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.8964741230010986s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 5.91278076171875e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.26300978660583496s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.02101612091064453s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006709098815917969s
Believability | Calculation of trust value for Human Phenotype Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-hp_x1 took 2.881387710571289s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.00032401084899902344s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.26280808448791504s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02068185806274414s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.00103759765625s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-hpio took 2.909085750579834s
Availability | SPARQL endpoint availability check for HUGO took 4.2438507080078125e-05s
Availability | VoID file availability check for HUGO took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for HUGO took 0.2759668827056885s
Reputation | Calculation of the PageRank for HUGO took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for HUGO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.963180541992188e-05s
Believability | Calculation of trust value for HUGO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-hugo took 2.944101333618164s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.9114227294921875e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.25045180320739746s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02124190330505371s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0007097721099853516s
Believability | Calculation of trust value for Information Artifact Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-iao took 2.872164487838745s
Availability | SPARQL endpoint availability check for ICD10 took 4.315376281738281e-05s
Availability | VoID file availability check for ICD10 took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for ICD10 took 0.25620555877685547s
Reputation | Calculation of the PageRank for ICD10 took 0.021002769470214844s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008881092071533203s
Believability | Calculation of trust value for ICD10 took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-icd10 took 2.856240749359131s
Availability | SPARQL endpoint availability check for ICD10CM took 4.363059997558594e-05s
Availability | VoID file availability check for ICD10CM took 0.0003235340118408203s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.24788808822631836s
Reputation | Calculation of the PageRank for ICD10CM took 0.021611452102661133s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.000946044921875s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0007624626159667969s
Believability | Calculation of trust value for ICD10CM took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.900383234024048s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.410743713378906e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0003495216369628906s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.2520179748535156s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.02103710174560547s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00016188621520996094s
Believability | Calculation of trust value for ICD-10-PCS took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.856903553009033s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.363059997558594e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.2626149654388428s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006427764892578125s
Believability | Calculation of trust value for International Classification of Diseases took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.8839468955993652s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2782158851623535s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004582405090332031s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.800524950027466s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.38690185546875e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2493290901184082s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0009109973907470703s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.001352548599243164s
Believability | Calculation of trust value for International Classification for Nursing Practice took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-icnp took 2.8981645107269287s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 5.0067901611328125e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2518343925476074s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020769119262695312s
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.00070953369140625s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004646778106689453s
Believability | Calculation of trust value for International Classification of Primary Care took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-icpc took 2.8091461658477783s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.3392181396484375e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2615213394165039s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020761966705322266s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008673667907714844s
Believability | Calculation of trust value for ICPC-2 PLUS took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.853376865386963s
Availability | SPARQL endpoint availability check for ICPS Network took 4.363059997558594e-05s
Availability | VoID file availability check for ICPS Network took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.25492286682128906s
Reputation | Calculation of the PageRank for ICPS Network took 0.02079153060913086s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002219676971435547s
Believability | Calculation of trust value for ICPS Network took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icps took 2.8265485763549805s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2575807571411133s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0009062290191650391s
Believability | Calculation of trust value for Infectious Disease Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ido took 2.8484482765197754s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 6.079673767089844e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2494797706604004s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.021146535873413086s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0013003349304199219s
Believability | Calculation of trust value for Brucellosis Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-idobru took 2.9041590690612793s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.23978805541992188s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013041496276855469s
Believability | Calculation of trust value for Malaria Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-idomal took 2.737518310546875s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 6.914138793945312e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2369847297668457s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020330190658569336s
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.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00033020973205566406s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-iev took 2.7336647510528564s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.267692565917969e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.23420119285583496s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015163421630859375s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-imgt took 2.7160332202911377s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.315376281738281e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2742280960083008s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005240440368652344s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-imr took 2.8516087532043457s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2742433547973633s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020394563674926758s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007956027984619141s
Believability | Calculation of trust value for Interaction Network Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ino took 2.9163498878479004s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.172325134277344e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.24900484085083008s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 2.9802322387695312e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 1.6927719116210938e-05s
INFO | --- Analysis for bioportal-invertebrata took 2.822510242462158s
Availability | SPARQL endpoint availability check for IxnO took 4.744529724121094e-05s
Availability | VoID file availability check for IxnO took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for IxnO took 0.25711894035339355s
Reputation | Calculation of the PageRank for IxnO took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for IxnO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018596649169921875s
Believability | Calculation of trust value for IxnO took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ixno took 2.826875925064087s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.1961669921875e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.24364328384399414s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020880699157714844s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00037860870361328125s
Believability | Calculation of trust value for SysMO-JERM took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-jerm took 2.85683012008667s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.24840068817138672s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 2.8133392333984375e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-kisao took 2.824662208557129s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.1484832763671875e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2637321949005127s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0001983642578125s
Believability | Calculation of trust value for Loggerhead nesting took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-lhn took 2.8615076541900635s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0002193450927734375s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.2788257598876953s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0001983642578125s
Believability | Calculation of trust value for Lipid Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-lipro took 2.805461883544922s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.1961669921875e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.2362077236175537s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.00095367431640625s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0020503997802734375s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-lnc took 2.8654415607452393s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 7.486343383789062e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2596604824066162s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006372928619384766s
Believability | Calculation of trust value for Mouse adult gross anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ma took 2.8461310863494873s
Availability | SPARQL endpoint availability check for Multiple alignment took 9.703636169433594e-05s
Availability | VoID file availability check for Multiple alignment took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.27765560150146484s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00019550323486328125s
Believability | Calculation of trust value for Multiple alignment took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mao took 2.867811918258667s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.363059997558594e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2596611976623535s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006959438323974609s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mat took 2.7597670555114746s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.2438507080078125e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.26216745376586914s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004200935363769531s
Believability | Calculation of trust value for Breast tissue cell lines took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-mcbcc took 2.851861000061035s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Cell line ontology took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.23597955703735352s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0009298324584960938s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0008459091186523438s
Believability | Calculation of trust value for Cell line ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-mccl took 2.8466527462005615s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.24993157386779785s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020033597946166992s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.00141143798828125s
Believability | Calculation of trust value for Cell line ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.79260516166687s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.220008850097656e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.27632641792297363s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00022912025451660156s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mcv took 2.796064853668213s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.315376281738281e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2379450798034668s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001690387725830078s
Believability | Calculation of trust value for Master Drug Data Base took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-mddb took 2.796997308731079s
Availability | SPARQL endpoint availability check for MedDRA took 4.363059997558594e-05s
Availability | VoID file availability check for MedDRA took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for MedDRA took 0.24672794342041016s
Reputation | Calculation of the PageRank for MedDRA took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011410713195800781s
Believability | Calculation of trust value for MedDRA took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mdr took 2.780641794204712s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.3392181396484375e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.27713727951049805s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020755290985107422s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009036064147949219s
Believability | Calculation of trust value for MedlinePlus Health Topics took 7.62939453125e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.8930561542510986s
Availability | SPARQL endpoint availability check for MeGO took 4.291534423828125e-05s
Availability | VoID file availability check for MeGO took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for MeGO took 0.2620863914489746s
Reputation | Calculation of the PageRank for MeGO took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for MeGO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0009601116180419922s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00017380714416503906s
Believability | Calculation of trust value for MeGO took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-mego took 2.7929859161376953s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.2438507080078125e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.234022855758667s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020310401916503906s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018432140350341797s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-mesh-owl took 2.8365485668182373s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00030350685119628906s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.27018165588378906s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006229877471923828s
Believability | Calculation of trust value for Mental Functioning Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mf took 2.8369357585906982s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.267692565917969e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.24585628509521484s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005474090576171875s
Believability | Calculation of trust value for Medaka fish anatomy and development took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mfo took 2.8205809593200684s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0010960102081298828s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2534213066101074s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007421970367431641s
Believability | Calculation of trust value for Emotion Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-mfoem took 2.8733701705932617s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 9.226799011230469e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2646019458770752s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010418891906738281s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mhc took 2.863321304321289s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.291534423828125e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2613210678100586s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020269393920898438s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006899833679199219s
Believability | Calculation of trust value for Protein-protein interaction took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mi took 2.8247475624084473s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.5299530029296875e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2579836845397949s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007457733154296875s
Believability | Calculation of trust value for Mosquito insecticide resistance took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-miro took 2.9984967708587646s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.2749814987182617s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00014328956604003906s
Believability | Calculation of trust value for Measurement Method Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-mmo took 2.9954745769500732s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for MGED Ontology took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.2547597885131836s
Reputation | Calculation of the PageRank for MGED Ontology took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0004315376281738281s
Believability | Calculation of trust value for MGED Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-mo took 2.93894100189209s
Availability | SPARQL endpoint availability check for Protein modification took 4.1961669921875e-05s
Availability | VoID file availability check for Protein modification took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2655787467956543s
Reputation | Calculation of the PageRank for Protein modification took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00022292137145996094s
Believability | Calculation of trust value for Protein modification took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-mod took 2.8167037963867188s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.291534423828125e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.00030350685119628906s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.27884960174560547s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02042102813720703s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006766319274902344s
Believability | Calculation of trust value for Mammalian phenotype took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mp took 2.8847861289978027s
Availability | SPARQL endpoint availability check for Mouse pathology took 5.3882598876953125e-05s
Availability | VoID file availability check for Mouse pathology took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2820878028869629s
Reputation | Calculation of the PageRank for Mouse pathology took 0.021706342697143555s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0005199909210205078s
Believability | Calculation of trust value for Mouse pathology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mpath took 2.788301467895508s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.220008850097656e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.25551724433898926s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003573894500732422s
Believability | Calculation of trust value for Mass spectrometry took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ms took 2.815523862838745s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.172325134277344e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.29155707359313965s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020725011825561523s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0020558834075927734s
Believability | Calculation of trust value for Medical Subject Headings took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-msh took 2.8947713375091553s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.3392181396484375e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.00033402442932128906s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2752993106842041s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00018167495727539062s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mthch took 2.9103477001190186s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.2647244930267334s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008373260498046875s
Believability | Calculation of trust value for Natural Products Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-natpro took 2.8602211475372314s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.3392181396484375e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2506704330444336s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008425712585449219s
Believability | Calculation of trust value for NCBI organismal classification took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.825956344604492s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.27131032943725586s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0020096302032470703s
Believability | Calculation of trust value for NCI Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-ncit took 2.8092238903045654s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.1484832763671875e-05s
Availability | VoID file availability check for National Drug Data File took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.27643918991088867s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006196498870849609s
Believability | Calculation of trust value for National Drug Data File took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-nddf took 2.887856960296631s
Availability | SPARQL endpoint availability check for National Drug File took 8.916854858398438e-05s
Availability | VoID file availability check for National Drug File took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2548961639404297s
Reputation | Calculation of the PageRank for National Drug File took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for National Drug File took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012302398681640625s
Believability | Calculation of trust value for National Drug File took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.7657995223999023s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.172325134277344e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2607743740081787s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011813640594482422s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.841703414916992s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0003802776336669922s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2679288387298584s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.02115488052368164s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006608963012695312s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-neomark took 2.8309731483459473s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.24984979629516602s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020923376083374023s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.0001266002655029297s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.9009604454040527s
Availability | SPARQL endpoint availability check for NIFSTD took 4.57763671875e-05s
Availability | VoID file availability check for NIFSTD took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.2634694576263428s
Reputation | Calculation of the PageRank for NIFSTD took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.001913309097290039s
Believability | Calculation of trust value for NIFSTD took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nif took 2.800619125366211s
Availability | SPARQL endpoint availability check for NIF Cell took 4.220008850097656e-05s
Availability | VoID file availability check for NIF Cell took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2687184810638428s
Reputation | Calculation of the PageRank for NIF Cell took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013568401336669922s
Believability | Calculation of trust value for NIF Cell took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.8875045776367188s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.2438507080078125e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.27467942237854004s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020479202270507812s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014276504516601562s
Believability | Calculation of trust value for NIF Dysfunction took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.815999746322632s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0003986358642578125s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2543680667877197s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02058863639831543s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 3.337860107421875e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005481243133544922s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-nigo took 2.7798049449920654s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.172325134277344e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.00021791458129882812s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2383730411529541s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005686283111572266s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nmr took 2.8322250843048096s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.27602386474609375s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.021048545837402344s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011944770812988281s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.885301351547241s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 5.555152893066406e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.2602653503417969s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011858940124511719s
Believability | Calculation of trust value for NanoParticle Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-npo took 2.8404195308685303s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.076957702636719e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.27881741523742676s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007138252258300781s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-oae took 2.8534743785858154s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.315376281738281e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.24938035011291504s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014629364013671875s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-obi took 2.8936843872070312s
Availability | SPARQL endpoint availability check for OBOE took 4.4345855712890625e-05s
Availability | VoID file availability check for OBOE took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for OBOE took 0.27781224250793457s
Reputation | Calculation of the PageRank for OBOE took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for OBOE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011014938354492188s
Believability | Calculation of trust value for OBOE took 7.62939453125e-06s
INFO | --- Analysis for bioportal-oboe took 2.8807318210601807s
Availability | SPARQL endpoint availability check for OBOE SBC took 7.462501525878906e-05s
Availability | VoID file availability check for OBOE SBC took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2447521686553955s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007956027984619141s
Believability | Calculation of trust value for OBOE SBC took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.8347699642181396s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.262831449508667s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020238399505615234s
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.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005981922149658203s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ocre took 2.871763229370117s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 5.3882598876953125e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.27629804611206055s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008406639099121094s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 7.62939453125e-06s
INFO | --- Analysis for bioportal-odgi took 2.848904848098755s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2698509693145752s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0008671283721923828s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.001005411148071289s
Believability | Calculation of trust value for Ontology for Genetic Interval took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ogi took 2.818213939666748s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.553794860839844e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.24736666679382324s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020371198654174805s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002827644348144531s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-ogmd took 2.8560996055603027s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.25301265716552734s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006768703460693359s
Believability | Calculation of trust value for Ontology for General Medical Science took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ogms took 2.8442318439483643s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.220008850097656e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2514486312866211s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020283937454223633s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011551380157470703s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-omim took 2.814117908477783s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.263641357421875s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003628730773925781s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-omit took 2.8481290340423584s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.24767589569091797s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005953311920166016s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-omrse took 2.826932191848755s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.839897155761719e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.24916291236877441s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007567405700683594s
Believability | Calculation of trust value for Ontology of Data Mining took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ontodm took 2.821331024169922s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.26526498794555664s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020219802856445312s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00023365020751953125s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-ontodt took 2.8500993251800537s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.220008850097656e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2576167583465576s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0005943775177001953s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.824239730834961s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.076957702636719e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.24409699440002441s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020219087600708008s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009465217590332031s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-opl took 2.8052444458007812s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.3392181396484375e-05s
Availability | VoID file availability check for Phenotypic quality took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.278378963470459s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008699893951416016s
Believability | Calculation of trust value for Phenotypic quality took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-pato took 2.8584437370300293s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.029273986816406e-05s
Availability | VoID file availability check for Physician Data Query took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2666311264038086s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0007998943328857422s
Believability | Calculation of trust value for Physician Data Query took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-pdq took 2.829279661178589s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 8.535385131835938e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.24008750915527344s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008289813995361328s
Believability | Calculation of trust value for Pediatric Terminology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-pedterm took 2.7926511764526367s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.27081966400146484s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020209312438964844s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00018906593322753906s
Believability | Calculation of trust value for Parasite Experiment Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-peo took 2.8159377574920654s
Availability | SPARQL endpoint availability check for PHARE took 4.1961669921875e-05s
Availability | VoID file availability check for PHARE took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for PHARE took 0.2639596462249756s
Reputation | Calculation of the PageRank for PHARE took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for PHARE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006301403045654297s
Believability | Calculation of trust value for PHARE took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-phare took 2.7841079235076904s
Availability | SPARQL endpoint availability check for PKO_Re took 4.5299530029296875e-05s
Availability | VoID file availability check for PKO_Re took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2666940689086914s
Reputation | Calculation of the PageRank for PKO_Re took 0.021363258361816406s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0008661746978759766s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00020360946655273438s
Believability | Calculation of trust value for PKO_Re took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-pko took 2.7532565593719482s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.887580871582031e-05s
Availability | VoID file availability check for PMA 2010 took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.24894976615905762s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020655393600463867s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.000926971435546875s
Believability | Calculation of trust value for PMA 2010 took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-pma took 2.7776947021484375s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 5.14984130859375e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2556464672088623s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001614093780517578s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-pmr took 2.8699562549591064s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Plant Anatomy took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2622699737548828s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.0202944278717041s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0003814697265625s
Believability | Calculation of trust value for Plant Anatomy took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-po took 2.8210387229919434s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.100799560546875e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0003204345703125s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2754058837890625s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.413459777832031e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.8420591354370117s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Plant Ontology took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.24060320854187012s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00043201446533203125s
Believability | Calculation of trust value for Plant Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.746443510055542s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.076957702636719e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2838289737701416s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006608963012695312s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-pr took 2.8924732208251953s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.1961669921875e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2633697986602783s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.000263214111328125s
Believability | Calculation of trust value for Proteomics data and process provenance took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-propreo took 2.8954505920410156s
Availability | SPARQL endpoint availability check for Pathway ontology took 7.43865966796875e-05s
Availability | VoID file availability check for Pathway ontology took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.35158419609069824s
Reputation | Calculation of the PageRank for Pathway ontology took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012874603271484375s
Believability | Calculation of trust value for Pathway ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pw took 2.9674606323242188s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.2615354061126709s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-qibo took 2.7922706604003906s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.220008850097656e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.2776310443878174s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0018014907836914062s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 7.62939453125e-06s
INFO | --- Analysis for bioportal-rcd took 2.8937220573425293s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2532820701599121s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02211141586303711s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00014257431030273438s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-rctontology took 2.8431525230407715s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0003726482391357422s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.25379109382629395s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0006971359252929688s
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 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-repo took 2.78304386138916s
Availability | SPARQL endpoint availability check for Physico-chemical process took 6.079673767089844e-05s
Availability | VoID file availability check for Physico-chemical process took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2578928470611572s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00018787384033203125s
Believability | Calculation of trust value for Physico-chemical process took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-rex took 2.847852945327759s
Availability | SPARQL endpoint availability check for RadLex took 4.100799560546875e-05s
Availability | VoID file availability check for RadLex took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for RadLex took 0.26840829849243164s
Reputation | Calculation of the PageRank for RadLex took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for RadLex took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015354156494140625s
Believability | Calculation of trust value for RadLex took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-rid took 2.9111318588256836s
Availability | SPARQL endpoint availability check for RNA ontology took 4.291534423828125e-05s
Availability | VoID file availability check for RNA ontology took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.24087309837341309s
Reputation | Calculation of the PageRank for RNA ontology took 0.021326065063476562s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005397796630859375s
Believability | Calculation of trust value for RNA ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-rnao took 2.800601005554199s
Availability | SPARQL endpoint availability check for Role Ontology took 4.887580871582031e-05s
Availability | VoID file availability check for Role Ontology took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2736625671386719s
Reputation | Calculation of the PageRank for Role Ontology took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018715858459472656s
Believability | Calculation of trust value for Role Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-roleo took 2.9028024673461914s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.00021767616271972656s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.2462613582611084s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.021277189254760742s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0008237361907958984s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00020503997802734375s
Believability | Calculation of trust value for Rat Strain Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-rs took 2.819685697555542s
Availability | SPARQL endpoint availability check for RxNORM took 4.172325134277344e-05s
Availability | VoID file availability check for RxNORM took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for RxNORM took 0.24368572235107422s
Reputation | Calculation of the PageRank for RxNORM took 0.02020096778869629s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0005962848663330078s
Believability | Calculation of trust value for RxNORM took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.825900077819824s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.1484832763671875e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.24353480339050293s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010521411895751953s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-sao took 2.802344560623169s
Availability | SPARQL endpoint availability check for Systems Biology took 4.1484832763671875e-05s
Availability | VoID file availability check for Systems Biology took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.26088786125183105s
Reputation | Calculation of the PageRank for Systems Biology took 0.02134394645690918s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0009808540344238281s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0005228519439697266s
Believability | Calculation of trust value for Systems Biology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-sbo took 2.804630994796753s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.256868839263916s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.0201873779296875s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010418891906738281s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-sbro took 2.7720000743865967s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.26514506340026855s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013353824615478516s
Believability | Calculation of trust value for Sleep Domain Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-sdo took 2.8445181846618652s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.172325134277344e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.28913378715515137s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.021132946014404297s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00034165382385253906s
Believability | Calculation of trust value for Sample processing and separation techniques took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-sep took 2.8848187923431396s
Availability | SPARQL endpoint availability check for Student Health Record took 4.0531158447265625e-05s
Availability | VoID file availability check for Student Health Record took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2360069751739502s
Reputation | Calculation of the PageRank for Student Health Record took 0.020264387130737305s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.000431060791015625s
Believability | Calculation of trust value for Student Health Record took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-shr took 2.7357938289642334s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.24831032752990723s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012218952178955078s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-sio took 2.861701250076294s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.1484832763671875e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.260577917098999s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0002105236053466797s
Believability | Calculation of trust value for Situation-Based Access Control took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-sitbac took 2.828385829925537s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.220008850097656e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.2674543857574463s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.001962900161743164s
Believability | Calculation of trust value for SNOMED Clinical Terms took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-snomedct took 2.8488476276397705s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.28957700729370117s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020957231521606445s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006589889526367188s
Believability | Calculation of trust value for SNP-Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-snpo took 2.8662514686584473s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.1484832763671875e-05s
Availability | VoID file availability check for Sequence types and features took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2444157600402832s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005805492401123047s
Believability | Calculation of trust value for Sequence types and features took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.8371496200561523s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.0531158447265625e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.27573204040527344s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0016012191772460938s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-sopharm took 2.788393259048462s
Availability | SPARQL endpoint availability check for SoyOntology took 4.172325134277344e-05s
Availability | VoID file availability check for SoyOntology took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.2781555652618408s
Reputation | Calculation of the PageRank for SoyOntology took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001361370086669922s
Believability | Calculation of trust value for SoyOntology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-soy took 2.877617835998535s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Spider Ontology took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.270341157913208s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.000316619873046875s
Believability | Calculation of trust value for Spider Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-spd took 2.835775375366211s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2720458507537842s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00027489662170410156s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-spto took 2.9501471519470215s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 7.43865966796875e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.27711963653564453s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004620552062988281s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-sso took 2.909686803817749s
Availability | SPARQL endpoint availability check for Software Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Software Ontology took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.25473451614379883s
Reputation | Calculation of the PageRank for Software Ontology took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Software Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00043201446533203125s
Believability | Calculation of trust value for Software Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-swo took 2.811622142791748s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 5.459785461425781e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2617783546447754s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00024890899658203125s
Believability | Calculation of trust value for Tick gross anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-tads took 2.8423547744750977s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2787954807281494s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008978843688964844s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-tao took 2.895430564880371s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.029273986816406e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2516481876373291s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.559226989746094e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-taxrank took 2.810579776763916s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.100799560546875e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.2743666172027588s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 6.604194641113281e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-teddy took 2.8548526763916016s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2384655475616455s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008056163787841797s
Believability | Calculation of trust value for Time Event Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-teo took 2.804549217224121s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.1961669921875e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2591402530670166s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00039124488830566406s
Believability | Calculation of trust value for Mosquito gross anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-tgma took 2.868300437927246s
Availability | SPARQL endpoint availability check for thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for thesaurus took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for thesaurus took 0.24901103973388672s
Reputation | Calculation of the PageRank for thesaurus took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.341934204101562e-05s
Believability | Calculation of trust value for thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-thesaurus took 2.794327735900879s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.0531158447265625e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.27585887908935547s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020229101181030273s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003368854522705078s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.8176186084747314s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.23508930206298828s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008456707000732422s
Believability | Calculation of trust value for Translational Medicine Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-tmo took 2.767935037612915s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.25543785095214844s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.021059274673461914s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00016355514526367188s
Believability | Calculation of trust value for Plant Trait Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-to took 2.809645414352417s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for TOK_Ontology took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.24602270126342773s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020949840545654297s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00019359588623046875s
Believability | Calculation of trust value for TOK_Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-tok took 2.863717555999756s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.2601134777069092s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019407272338867188s
Believability | Calculation of trust value for Teleost taxonomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-tto took 2.9176907539367676s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.268383264541626s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010323524475097656s
Believability | Calculation of trust value for Uber anatomy ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-uberon took 2.8963682651519775s
Availability | SPARQL endpoint availability check for Units Ontology took 6.437301635742188e-05s
Availability | VoID file availability check for Units Ontology took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.2602386474609375s
Reputation | Calculation of the PageRank for Units Ontology took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00021147727966308594s
Believability | Calculation of trust value for Units Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-unitsontology took 2.8721299171447754s
Availability | SPARQL endpoint availability check for Units of measurement took 5.316734313964844e-05s
Availability | VoID file availability check for Units of measurement took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2780916690826416s
Reputation | Calculation of the PageRank for Units of measurement took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002942085266113281s
Believability | Calculation of trust value for Units of measurement took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-uo took 2.8966267108917236s
Availability | SPARQL endpoint availability check for VANDF took 4.2438507080078125e-05s
Availability | VoID file availability check for VANDF took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for VANDF took 0.2601497173309326s
Reputation | Calculation of the PageRank for VANDF took 0.021225690841674805s
Interlinking | Calculation of Degree of Connection for VANDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007219314575195312s
Believability | Calculation of trust value for VANDF took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-vandf took 2.826638698577881s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 5.698204040527344e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2658193111419678s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00043702125549316406s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-vao took 2.8800392150878906s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.1961669921875e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.27558374404907227s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006210803985595703s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-vhog took 2.867436647415161s
Availability | SPARQL endpoint availability check for VIVO took 4.410743713378906e-05s
Availability | VoID file availability check for VIVO took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for VIVO took 0.2600870132446289s
Reputation | Calculation of the PageRank for VIVO took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00035071372985839844s
Believability | Calculation of trust value for VIVO took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-vivo took 2.7988834381103516s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.26628828048706055s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.001262664794921875s
Believability | Calculation of trust value for Vaccine Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-vo took 2.7978479862213135s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.24802732467651367s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020051002502441406s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-vt took 2.8481199741363525s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.315376281738281e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.00022125244140625s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2656376361846924s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004885196685791016s
Believability | Calculation of trust value for C. elegans gross anatomy took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-wbbt took 2.854018449783325s
Availability | SPARQL endpoint availability check for C. elegans development took 4.1484832763671875e-05s
Availability | VoID file availability check for C. elegans development took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2527616024017334s
Reputation | Calculation of the PageRank for C. elegans development took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.458427429199219e-05s
Believability | Calculation of trust value for C. elegans development took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-wbls took 2.826634168624878s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 7.414817810058594e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.25936365127563477s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.440017700195312e-05s
Believability | Calculation of trust value for C. elegans phenotype took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-wbphenotype took 2.849705934524536s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.124641418457031e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.27892184257507324s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005750656127929688s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-who took 2.8325445652008057s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.1961669921875e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.23822021484375s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020947694778442383s
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.0009133815765380859s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0007810592651367188s
Believability | Calculation of trust value for Xenopus anatomy and development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-xao took 2.8150367736816406s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.23641061782836914s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023365020751953125s
Believability | Calculation of trust value for Experimental Conditions Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-xco took 2.8514957427978516s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.220008850097656e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.2514042854309082s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020245790481567383s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002613067626953125s
Believability | Calculation of trust value for Yeast phenotypes took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-ypo took 2.7788028717041016s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.220008850097656e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.26344990730285645s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.00079345703125s
Believability | Calculation of trust value for Zebrafish anatomy and development took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-zfa took 2.838531494140625s
Availability | SPARQL endpoint availability check for BioSamples RDF took 5.4836273193359375e-05s
Availability | VoID file availability check for BioSamples RDF took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.26168131828308105s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.3113021850585938e-05s
INFO | --- Analysis for biosamples-rdf took 2.8281548023223877s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 4.172325134277344e-05s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0003848075866699219s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.28287291526794434s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020572185516357422s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011205673217773438s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 6.4373016357421875e-06s
INFO | --- Analysis for bis-linked-data took 2.8780148029327393s
Availability | SPARQL endpoint availability check for Bitzi took 4.1961669921875e-05s
Availability | VoID file availability check for Bitzi took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Bitzi took 0.29616236686706543s
Reputation | Calculation of the PageRank for Bitzi took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Bitzi took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bitzi took 7.62939453125e-06s
INFO | --- Analysis for bitzi took 2.8428521156311035s
Availability | SPARQL endpoint availability check for BizkaiSense took 5.245208740234375e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.24774861335754395s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 2.9325485229492188e-05s
Believability | Calculation of trust value for BizkaiSense took 7.3909759521484375e-06s
INFO | --- Analysis for bizkaisense took 2.8840043544769287s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.1961669921875e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.25557994842529297s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0040740966796875e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.3909759521484375e-06s
INFO | --- Analysis for blabla-itemlist took 2.8049983978271484s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.100799560546875e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00035953521728515625s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.25356268882751465s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.021117448806762695s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.1948089599609375e-05s
Believability | Calculation of trust value for blabla.itemlist took 8.106231689453125e-06s
INFO | --- Analysis for blabla_itemlist took 2.8313775062561035s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.344405174255371s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.2506141662597656s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.556510925292969e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for bluk-bnb took 4.305830240249634s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.220008850097656e-05s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2426300048828125s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.719329833984375e-05s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.3909759521484375e-06s
INFO | --- Analysis for bpr took 2.885486364364624s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.291534423828125e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.24875473976135254s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.67572021484375e-05s
Believability | Calculation of trust value for Brazilian Politicians took 1.1682510375976562e-05s
INFO | --- Analysis for brazilian-politicians took 2.8632280826568604s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.029273986816406e-05s
Availability | VoID file availability check for BrazilianCities took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.267225980758667s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.1948089599609375e-05s
Believability | Calculation of trust value for BrazilianCities took 1.239776611328125e-05s
INFO | --- Analysis for braziliancities took 2.8367393016815186s
Availability | SPARQL endpoint availability check for Bricklink took 4.100799560546875e-05s
Availability | VoID file availability check for Bricklink took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Bricklink took 0.25498342514038086s
Reputation | Calculation of the PageRank for Bricklink took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.604194641113281e-05s
Believability | Calculation of trust value for Bricklink took 7.62939453125e-06s
INFO | --- Analysis for bricklink took 2.861703872680664s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.230244636535645s
Availability | VoID file availability check for British Museum Collection took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2624485492706299s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020360708236694336s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.361701965332031e-05s
Believability | Calculation of trust value for British Museum Collection took 1.0967254638671875e-05s
INFO | --- Analysis for british-museum-collection took 63.13512563705444s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.2438507080078125e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.2645719051361084s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020597219467163086s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.886222839355469e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 7.62939453125e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.9678726196289062s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 6.604194641113281e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.26261043548583984s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.8371810913085938e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 7.152557373046875e-06s
INFO | --- Analysis for bsv took 2.7939579486846924s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.2438507080078125e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.23503565788269043s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 2.86102294921875e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.239776611328125e-05s
INFO | --- Analysis for bund-offener-haushalt took 2.836690664291382s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.1961669921875e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.25997400283813477s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 2.7418136596679688e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 7.62939453125e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.927626848220825s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 4.267692565917969e-05s
Availability | VoID file availability check for business.data.gov.uk took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.27640604972839355s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 4.982948303222656e-05s
Believability | Calculation of trust value for business.data.gov.uk took 7.152557373046875e-06s
INFO | --- Analysis for business-data-gov-uk took 2.8498640060424805s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.3392181396484375e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.25199222564697266s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 2.86102294921875e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.152557373046875e-06s
INFO | --- Analysis for cabbage took 2.8819124698638916s
Availability | SPARQL endpoint availability check for cablegate took 4.4345855712890625e-05s
Availability | VoID file availability check for cablegate took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for cablegate took 0.307178258895874s
Reputation | Calculation of the PageRank for cablegate took 0.020257949829101562s
Interlinking | Calculation of Degree of Connection for cablegate took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for cablegate took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.127357482910156e-05s
Believability | Calculation of trust value for cablegate took 1.1682510375976562e-05s
INFO | --- Analysis for cablegate took 2.9268784523010254s
Availability | SPARQL endpoint availability check for Calames took 5.555152893066406e-05s
Availability | VoID file availability check for Calames took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Calames took 0.23846030235290527s
Reputation | Calculation of the PageRank for Calames took 0.02006697654724121s
Interlinking | Calculation of Degree of Connection for Calames took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Calames took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Calames took 4.839897155761719e-05s
Believability | Calculation of trust value for Calames took 7.152557373046875e-06s
INFO | --- Analysis for calames took 2.7688663005828857s
Availability | SPARQL endpoint availability check for can-link took 4.649162292480469e-05s
Availability | VoID file availability check for can-link took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for can-link took 0.23828434944152832s
Reputation | Calculation of the PageRank for can-link took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for can-link took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for can-link took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for can-link took 2.7894973754882812e-05s
Believability | Calculation of trust value for can-link took 6.4373016357421875e-06s
INFO | --- Analysis for can-link took 2.7946364879608154s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 4.172325134277344e-05s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2684948444366455s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 6.4373016357421875e-06s
INFO | --- Analysis for cap-italy-rdf took 2.8622028827667236s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.1484832763671875e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2640342712402344s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.695487976074219e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 7.152557373046875e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.8840668201446533s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.1484832763671875e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.27684998512268066s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020900249481201172s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.0517578125e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.3589859008789062e-05s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.876194715499878s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.5299530029296875e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.27811098098754883s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.632110595703125e-05s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 6.67572021484375e-06s
INFO | --- Analysis for ce4r took 2.8692562580108643s
Availability | SPARQL endpoint availability check for Charging Stations took 4.124641418457031e-05s
Availability | VoID file availability check for Charging Stations took 0.00033974647521972656s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.27596282958984375s
Reputation | Calculation of the PageRank for Charging Stations took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.1948089599609375e-05s
Believability | Calculation of trust value for Charging Stations took 3.4332275390625e-05s
INFO | --- Analysis for charging-stations took 2.796555519104004s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.291534423828125e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.2808237075805664s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.266334533691406e-05s
Believability | Calculation of trust value for Chat Game corpus took 8.344650268554688e-06s
INFO | --- Analysis for chat-game-corpus took 2.772684097290039s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.482269287109375e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.24957036972045898s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007126331329345703s
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 6.9141387939453125e-06s
INFO | --- Analysis for chebi took 2.834812641143799s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.291534423828125e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0003113746643066406s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.23249530792236328s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.435943603515625e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 6.9141387939453125e-06s
INFO | --- Analysis for chem2bio2rdf took 2.802661895751953s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 5.1975250244140625e-05s
Availability | VoID file availability check for ChEMBL RDF took 0.00031685829162597656s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.2893664836883545s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.4836273193359375e-05s
Believability | Calculation of trust value for ChEMBL RDF took 7.3909759521484375e-06s
INFO | --- Analysis for chembl-rdf took 2.853213310241699s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.100799560546875e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.24855470657348633s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 2.8371810913085938e-05s
Believability | Calculation of trust value for ChemPedia RDF took 7.152557373046875e-06s
INFO | --- Analysis for chempedia-rdf took 2.902911901473999s
Availability | SPARQL endpoint availability check for Chronicling America took 7.104873657226562e-05s
Availability | VoID file availability check for Chronicling America took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.24672508239746094s
Reputation | Calculation of the PageRank for Chronicling America took 0.020864486694335938s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00011205673217773438s
Believability | Calculation of trust value for Chronicling America took 7.3909759521484375e-06s
INFO | --- Analysis for chronicling-america took 2.8081753253936768s
Availability | SPARQL endpoint availability check for ciard-ring took 4.1484832763671875e-05s
Availability | VoID file availability check for ciard-ring took 0.00036072731018066406s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2631652355194092s
Reputation | Calculation of the PageRank for ciard-ring took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for ciard-ring took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 3.933906555175781e-05s
Believability | Calculation of trust value for ciard-ring took 6.9141387939453125e-06s
INFO | --- Analysis for ciard-ring took 2.800593376159668s
Availability | SPARQL endpoint availability check for CIPFA took 4.220008850097656e-05s
Availability | VoID file availability check for CIPFA took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for CIPFA took 0.27864527702331543s
Reputation | Calculation of the PageRank for CIPFA took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.314018249511719e-05s
Believability | Calculation of trust value for CIPFA took 7.867813110351562e-06s
INFO | --- Analysis for cipfa took 2.864220380783081s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 4.315376281738281e-05s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.25847578048706055s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.021177053451538086s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00039505958557128906s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 7.62939453125e-06s
INFO | --- Analysis for ckan took 2.8165652751922607s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 4.076957702636719e-05s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2594931125640869s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 9.72747802734375e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 1.1444091796875e-05s
INFO | --- Analysis for clean-energy-data-reegle took 2.8267874717712402s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-afbo took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2603759765625s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.867813110351562e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.1920928955078125e-05s
INFO | --- Analysis for clld-afbo took 2.777341842651367s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.172325134277344e-05s
Availability | VoID file availability check for CLLD-APICS took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.24959349632263184s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020272254943847656s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.271766662597656e-05s
Believability | Calculation of trust value for CLLD-APICS took 6.4373016357421875e-06s
INFO | --- Analysis for clld-apics took 2.824016571044922s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2736649513244629s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020323514938354492s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.4809112548828125e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 6.67572021484375e-06s
INFO | --- Analysis for clld-ewave took 2.9313952922821045s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 5.0067901611328125e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2549862861633301s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020388126373291016s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.584426879882812e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 6.9141387939453125e-06s
INFO | --- Analysis for clld-glottolog took 2.7876641750335693s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.100799560546875e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.25557971000671387s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.390975952148438e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 7.62939453125e-06s
INFO | --- Analysis for clld-phoible took 2.7906336784362793s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.124641418457031e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.2896883487701416s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020264387130737305s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.200241088867188e-05s
Believability | Calculation of trust value for CLLD-SAILS took 6.9141387939453125e-06s
INFO | --- Analysis for clld-sails took 2.838498592376709s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.25577306747436523s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 7.748603820800781e-05s
Believability | Calculation of trust value for CLLD-WALS took 7.152557373046875e-06s
INFO | --- Analysis for clld-wals took 2.7906365394592285s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.24344348907470703s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.200241088867188e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.2874603271484375e-05s
INFO | --- Analysis for clld-wold took 2.864880323410034s
Availability | SPARQL endpoint availability check for COD inventory took 4.410743713378906e-05s
Availability | VoID file availability check for COD inventory took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for COD inventory took 0.2848165035247803s
Reputation | Calculation of the PageRank for COD inventory took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for COD inventory took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COD inventory took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for COD inventory took 2.9087066650390625e-05s
Believability | Calculation of trust value for COD inventory took 7.62939453125e-06s
INFO | --- Analysis for cod-inventory took 2.900198459625244s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.124641418457031e-05s
Availability | VoID file availability check for CODE Endpoint took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.23118138313293457s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020398855209350586s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.0040740966796875e-05s
Believability | Calculation of trust value for CODE Endpoint took 1.1682510375976562e-05s
INFO | --- Analysis for code-endpoint took 2.8477087020874023s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 4.291534423828125e-05s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.2868659496307373s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02032327651977539s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.0994415283203125e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 7.867813110351562e-06s
INFO | --- Analysis for coins-openuplabs took 2.913241147994995s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 4.076957702636719e-05s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.2722361087799072s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.647804260253906e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for colinda took 2.9172775745391846s
Availability | SPARQL endpoint availability check for CN  2012 took 4.2438507080078125e-05s
Availability | VoID file availability check for CN  2012 took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.24987363815307617s
Reputation | Calculation of the PageRank for CN  2012 took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.600120544433594e-05s
Believability | Calculation of trust value for CN  2012 took 7.867813110351562e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 2.922112226486206s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 8.630752563476562e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.23875975608825684s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.021221637725830078s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0008544921875s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.409385681152344e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 1.3113021850585938e-05s
INFO | --- Analysis for comments-on-literature-in-literature took 2.919947624206543s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 8.678436279296875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.24676871299743652s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 2.956390380859375e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 7.62939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.843538284301758s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.2438507080078125e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.2640998363494873s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.020191192626953125s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 2.7179718017578125e-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.8393607139587402s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.1484832763671875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.000316619873046875s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.24596738815307617s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.86102294921875e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 8.58306884765625e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.780954599380493s
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.00025343894958496094s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.2772538661956787s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02084827423095703s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.075599670410156e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 7.62939453125e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.897125005722046s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 4.1484832763671875e-05s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.2425553798675537s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.409385681152344e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 7.867813110351562e-06s
INFO | --- Analysis for comsode-d3-2 took 2.826035976409912s
Availability | SPARQL endpoint availability check for ConceptNet took 6.794929504394531e-05s
Availability | VoID file availability check for ConceptNet took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.2541694641113281s
Reputation | Calculation of the PageRank for ConceptNet took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.86102294921875e-05s
Believability | Calculation of trust value for ConceptNet took 7.867813110351562e-06s
INFO | --- Analysis for conceptnet took 2.845062494277954s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 6.723403930664062e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2680354118347168s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.6716461181640625e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 6.67572021484375e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.8462419509887695s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.124641418457031e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.273547887802124s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.8371810913085938e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 6.9141387939453125e-06s
INFO | --- Analysis for copac-library-catalogue took 2.8852593898773193s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.124641418457031e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.2363145351409912s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.651878356933594e-05s
Believability | Calculation of trust value for CopyrightTermBank took 6.9141387939453125e-06s
INFO | --- Analysis for copyrighttermbank took 2.7452144622802734s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 4.172325134277344e-05s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2565443515777588s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.021132707595825195s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.886222839355469e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 8.344650268554688e-06s
INFO | --- Analysis for core took 2.830348253250122s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.100799560546875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.00033211708068847656s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.24560141563415527s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 2.9802322387695312e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.344650268554688e-06s
INFO | --- Analysis for corn took 2.825348138809204s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.3392181396484375e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2745051383972168s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.0040740966796875e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 8.106231689453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 2.8516550064086914s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.673004150390625e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.2670586109161377s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.9087066650390625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.2874603271484375e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.8190553188323975s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 5.435943603515625e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.2642078399658203s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.021460771560668945s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0006809234619140625s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.650520324707031e-05s
Believability | Calculation of trust value for Cornetto1.2 took 7.3909759521484375e-06s
INFO | --- Analysis for cornetto took 2.8530373573303223s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.315376281738281e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.2618703842163086s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 3.218650817871094e-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.885246992111206s
Availability | SPARQL endpoint availability check for Courts thesaurus took 5.0067901611328125e-05s
Availability | VoID file availability check for Courts thesaurus took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2609255313873291s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 3.62396240234375e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.580352783203125e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for courts-thesaurus took 2.879395008087158s
Availability | SPARQL endpoint availability check for CPA 2008 took 4.2438507080078125e-05s
Availability | VoID file availability check for CPA 2008 took 0.00034427642822265625s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.2347545623779297s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.504753112792969e-05s
Believability | Calculation of trust value for CPA 2008 took 7.867813110351562e-06s
INFO | --- Analysis for cpa-2008 took 2.8194773197174072s
Availability | SPARQL endpoint availability check for CPC 2008 took 4.0531158447265625e-05s
Availability | VoID file availability check for CPC 2008 took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.24892640113830566s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.504753112792969e-05s
Believability | Calculation of trust value for CPC 2008 took 1.3113021850585938e-05s
INFO | --- Analysis for cpc-2008 took 2.822272300720215s
Availability | SPARQL endpoint availability check for CPV  2003 took 4.172325134277344e-05s
Availability | VoID file availability check for CPV  2003 took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.24904251098632812s
Reputation | Calculation of the PageRank for CPV  2003 took 0.020493745803833008s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.457069396972656e-05s
Believability | Calculation of trust value for CPV  2003 took 1.2159347534179688e-05s
INFO | --- Analysis for cpv-2003 took 2.836272954940796s
Availability | SPARQL endpoint availability check for CPV 2008 took 4.220008850097656e-05s
Availability | VoID file availability check for CPV 2008 took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.2580711841583252s
Reputation | Calculation of the PageRank for CPV 2008 took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.410743713378906e-05s
Believability | Calculation of trust value for CPV 2008 took 1.3113021850585938e-05s
INFO | --- Analysis for cpv-2008 took 2.8067257404327393s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 4.172325134277344e-05s
Availability | VoID file availability check for crowdsourcing-fb took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.2618410587310791s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 3.600120544433594e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 6.67572021484375e-06s
INFO | --- Analysis for crowdsourcing-fb took 2.9460432529449463s
Availability | SPARQL endpoint availability check for CRTM took 4.172325134277344e-05s
Availability | VoID file availability check for CRTM took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for CRTM took 0.2610499858856201s
Reputation | Calculation of the PageRank for CRTM took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.9087066650390625e-05s
Believability | Calculation of trust value for CRTM took 7.867813110351562e-06s
INFO | --- Analysis for crtm took 2.97522234916687s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.1961669921875e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.255023717880249s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.266334533691406e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 1.1920928955078125e-05s
INFO | --- Analysis for crystal-eye took 2.902407646179199s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 4.2438507080078125e-05s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.2685246467590332s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.410743713378906e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 7.867813110351562e-06s
INFO | --- Analysis for ctic-public-dataset took 2.8043694496154785s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.1961669921875e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0003197193145751953s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.2548196315765381s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.021090269088745117s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.24249267578125e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 1.2874603271484375e-05s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 2.839664936065674s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.7683103084564209s
Availability | VoID file availability check for CulturaLinkedData took 0.00029969215393066406s
Extra | Recovery of all triples for CulturaLinkedData took 143.37423753738403s
Performance | Total latancy measurement for CulturaLinkedData took 4.4466094970703125s
Amount of data | Number of triples check for CulturaLinkedData took 4.9456281661987305s
Interoperability | New terms check for CulturaLinkedData took 2.2349436283111572s
Versatility | Languages check for CulturaLinkedData took 61.98024010658264s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.039933681488037s
Interpretability | RDF structures check for CulturaLinkedData took 2.344656467437744s
Versatility | Serialization formats check for CulturaLinkedData took 4.369927644729614s
Availability | RDF dump link check for CulturaLinkedData took 0.2665743827819824s
License | MR license check for CulturaLinkedData took 2.5096826553344727s
License | HR license check for CulturaLinkedData took 63.81308698654175s
Amount of data | Number of property check for CulturaLinkedData took 0.18624544143676758s
Understandability | Number of label check for CulturaLinkedData took 2.866405963897705s
Understandability | URI regex check for CulturaLinkedData took 0.5616316795349121s
Understandability | Vocabs check for CulturaLinkedData took 2.1103386878967285s
Verifiability | Authors check for CulturaLinkedData took 2.027437210083008s
Verifiability | Publishers check for CulturaLinkedData took 0.24466991424560547s
Performance | Throughput check for CulturaLinkedData took 21.88304352760315s
Amount of data | Check the number of entities for CulturaLinkedData took 0.00011014938354492188s
Verifiability | Contribs. check for CulturaLinkedData took 0.28827905654907227s
Interlinking | sameAs chians check for CulturaLinkedData took 0.3351306915283203s
Interlinking | skos check for CulturaLinkedData took 0.45132946968078613s
Interlinking | skos check for CulturaLinkedData took 2.0279979705810547s
Timeliness | dataset update frequency check for CulturaLinkedData took 2.1287038326263428s
Currency | Creation date check for CulturaLinkedData took 0.4865686893463135s
Currency | Modification date check for CulturaLinkedData took 2.1814186573028564s
Rep.Conc. | URIs length for CulturaLinkedData took 65.59275841712952s
Interoperability | New vocabularies check for CulturaLinkedData took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 1.877671480178833s
Accuracy | Check Functional Property for CulturaLinkedData took 0.18527841567993164s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 1.9839279651641846s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 45.27798271179199s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6073839664459229s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.2768659591674805s
Consistency | Disjoint class check for CulturaLinkedData took 2.0339670181274414s
Consistency | Check Misplaced properties for CulturaLinkedData took 11.699872732162476s
Consistency | Misplaced classes for CulturaLinkedData took 4.266332387924194s
Consistency | Check Ontology hijacking for CulturaLinkedData took 38.07475709915161s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3891067504882812s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 9.187013387680054s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3912498950958252s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.18411636352539062s
Security | Sign check for CulturaLinkedData took 0.9895455837249756s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 17.044440746307373s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.9398202896118164s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021039724349975586s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.1457672119140625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 7.152557373046875e-06s
INFO | --- Analysis for culturalinkeddata took 669.929915189743s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 4.220008850097656e-05s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2647252082824707s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.6253204345703125e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ares-or took 3.2823357582092285s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.220008850097656e-05s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.2902085781097412s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020326614379882812s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.2901763916015625e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.1682510375976562e-05s
INFO | --- Analysis for cz-ares-rzp took 2.879865884780884s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 4.1961669921875e-05s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.290158748626709s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020457983016967773s
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.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.147125244140625e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 1.1205673217773438e-05s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.3528637886047363s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 4.00543212890625e-05s
Availability | VoID file availability check for Integrated pollution registry took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.23870444297790527s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.743171691894531e-05s
Believability | Calculation of trust value for Integrated pollution registry took 7.62939453125e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.866417407989502s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 5.3882598876953125e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.27436232566833496s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007212162017822266s
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 8.106231689453125e-06s
INFO | --- Analysis for cz-contracts took 2.845224380493164s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.124641418457031e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.26160287857055664s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.6464462280273438e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-courts took 2.9155139923095703s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 4.124641418457031e-05s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.00038504600524902344s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2677130699157715s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.266334533691406e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 7.3909759521484375e-06s
INFO | --- Analysis for cz-ctia-bans took 2.796234369277954s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 4.1484832763671875e-05s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.2560255527496338s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.0994415283203125e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 7.62939453125e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.8445096015930176s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 4.172325134277344e-05s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.25136899948120117s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.1948089599609375e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7757346630096436s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 4.1484832763671875e-05s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.25189805030822754s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 3.910064697265625e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 7.3909759521484375e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.8598036766052246s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 4.172325134277344e-05s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.26652979850769043s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.170967102050781e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 7.62939453125e-06s
INFO | --- Analysis for cz-ctia-sanctions took 2.751319169998169s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 4.100799560546875e-05s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.26285505294799805s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.021587133407592773s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.000934600830078125s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.315376281738281e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 7.152557373046875e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.834648609161377s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 4.267692565917969e-05s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2763650417327881s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.600120544433594e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 1.2159347534179688e-05s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.8607683181762695s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 4.100799560546875e-05s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.26331472396850586s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02022409439086914s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-czso-average-salaries took 2.823850393295288s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 5.245208740234375e-05s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.2605304718017578s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020140886306762695s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 6.67572021484375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 2.8640408515930176s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.38690185546875e-05s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.25128674507141113s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.02032184600830078s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.5762786865234375e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.9604644775390625e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 2.8222296237945557s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 4.1484832763671875e-05s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.00048828125s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2743544578552246s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.743171691894531e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-czso-job-applicants took 2.9390907287597656s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 4.2438507080078125e-05s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2495265007019043s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.02041792869567871s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.552436828613281e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 2.878929615020752s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 4.124641418457031e-05s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2561793327331543s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.600120544433594e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 7.867813110351562e-06s
INFO | --- Analysis for cz-czso-regions took 2.7990565299987793s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 4.076957702636719e-05s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2795071601867676s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.62396240234375e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 2.8188095092773438s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 4.124641418457031e-05s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2668449878692627s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020116806030273438s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.600120544433594e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 2.739548683166504s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 5.91278076171875e-05s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.27035045623779297s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.62396240234375e-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 2.850642442703247s
Availability | SPARQL endpoint availability check for ATC groups took 4.1484832763671875e-05s
Availability | VoID file availability check for ATC groups took 0.0003123283386230469s
Completeness | Calculation of interlinking completeness for ATC groups took 0.27544713020324707s
Reputation | Calculation of the PageRank for ATC groups took 0.020907878875732422s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for ATC groups took 8.845329284667969e-05s
Believability | Calculation of trust value for ATC groups took 7.3909759521484375e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.855868101119995s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 4.506111145019531e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.23366856575012207s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.4332275390625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 7.62939453125e-06s
INFO | --- Analysis for cz-fulfillments took 2.8807554244995117s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 4.2438507080078125e-05s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.2738673686981201s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.887580871582031e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ic took 2.84970760345459s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 4.601478576660156e-05s
Availability | VoID file availability check for List of Czech data boxes took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.26531124114990234s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 2.9087066650390625e-05s
Believability | Calculation of trust value for List of Czech data boxes took 1.7404556274414062e-05s
INFO | --- Analysis for cz-list-of-databoxes took 2.8335928916931152s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.267692565917969e-05s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.26563119888305664s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0008227825164794922s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.123283386230469e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.3909759521484375e-06s
INFO | --- Analysis for cz-nace took 2.906423807144165s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.220008850097656e-05s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2621951103210449s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.956390380859375e-05s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.152557373046875e-06s
INFO | --- Analysis for cz-nkod took 2.848026752471924s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 4.267692565917969e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.23616838455200195s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020572662353515625s
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.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.409385681152344e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 6.4373016357421875e-06s
INFO | --- Analysis for cz-orders took 2.8110148906707764s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 4.291534423828125e-05s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.2538297176361084s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.4345855712890625e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-ovm took 2.812626600265503s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 4.1484832763671875e-05s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2673759460449219s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.2901763916015625e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-ovm-agendas took 2.8034825325012207s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.295608520507812e-05s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.00037097930908203125s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2596592903137207s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.771087646484375e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.62939453125e-06s
INFO | --- Analysis for cz-ruian took 2.8749399185180664s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 4.3392181396484375e-05s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.2501804828643799s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.033348083496094e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 2.7945055961608887s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 4.673004150390625e-05s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.252504825592041s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sao-check-actions took 2.780313730239868s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 4.220008850097656e-05s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.00033736228942871094s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.24425244331359863s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020519733428955078s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.170967102050781e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 1.0728836059570312e-05s
INFO | --- Analysis for cz-sao-check-actions-law took 2.796295404434204s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 5.364418029785156e-05s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.24783039093017578s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.021792173385620117s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 7.62939453125e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.7956035137176514s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 8.702278137207031e-05s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.25385618209838867s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.3855438232421875e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.7618792057037354s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 4.792213439941406e-05s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0003604888916015625s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2350764274597168s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007045269012451172s
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.58306884765625e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.731189489364624s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 4.2438507080078125e-05s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.2705347537994385s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021099090576171875s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.886222839355469e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 8.344650268554688e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2.844921588897705s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 4.100799560546875e-05s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2409379482269287s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020586252212524414s
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.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.4809112548828125e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 2.7377169132232666s
Availability | SPARQL endpoint availability check for State funding providers took 4.220008850097656e-05s
Availability | VoID file availability check for State funding providers took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for State funding providers took 0.2470560073852539s
Reputation | Calculation of the PageRank for State funding providers took 0.020904541015625s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0010271072387695312s
Interlinking | Calculation of Clustering coefficient for State funding providers took 9.489059448242188e-05s
Believability | Calculation of trust value for State funding providers took 7.867813110351562e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 2.830287456512451s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 4.2438507080078125e-05s
Availability | VoID file availability check for Organizations active in R&D took 0.00032210350036621094s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.25444936752319336s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020581960678100586s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.100799560546875e-05s
Believability | Calculation of trust value for Organizations active in R&D took 7.867813110351562e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.74709415435791s
Availability | SPARQL endpoint availability check for R&D Programmes took 4.1484832763671875e-05s
Availability | VoID file availability check for R&D Programmes took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.26859211921691895s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020326614379882812s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.933906555175781e-05s
Believability | Calculation of trust value for R&D Programmes took 1.0967254638671875e-05s
INFO | --- Analysis for cz-vavai-programmes took 2.888340711593628s
Availability | SPARQL endpoint availability check for R&D Projects took 5.8650970458984375e-05s
Availability | VoID file availability check for R&D Projects took 0.00031447410583496094s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.2476029396057129s
Reputation | Calculation of the PageRank for R&D Projects took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.410743713378906e-05s
Believability | Calculation of trust value for R&D Projects took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-projects took 2.8490312099456787s
Availability | SPARQL endpoint availability check for Institutional research plans took 4.267692565917969e-05s
Availability | VoID file availability check for Institutional research plans took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.23932862281799316s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.0531158447265625e-05s
Believability | Calculation of trust value for Institutional research plans took 7.62939453125e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.8160548210144043s
Availability | SPARQL endpoint availability check for Results of R&D took 4.220008850097656e-05s
Availability | VoID file availability check for Results of R&D took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.25435805320739746s
Reputation | Calculation of the PageRank for Results of R&D took 0.02084946632385254s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.410743713378906e-05s
Believability | Calculation of trust value for Results of R&D took 8.106231689453125e-06s
INFO | --- Analysis for cz-vavai-results took 2.7944083213806152s
Availability | SPARQL endpoint availability check for Tenders in R&D took 4.315376281738281e-05s
Availability | VoID file availability check for Tenders in R&D took 0.0003247261047363281s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2560856342315674s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.076957702636719e-05s
Believability | Calculation of trust value for Tenders in R&D took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.839071750640869s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.32655954360961914s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0002532005310058594s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 146.2072126865387s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 0.9679429531097412s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 16.325891256332397s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.419621706008911s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 0.18099021911621094s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.2056877613067627s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.12961721420288086s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.23657679557800293s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.46579575538635254s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.4319596290588379s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 1.8111774921417236s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 77.13589239120483s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.20949530601501465s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 2.9935898780822754s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.6512515544891357s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.20622634887695312s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.44054341316223145s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.19444561004638672s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.372671365737915s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.128715515136719e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.19400787353515625s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 1.1383287906646729s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.7109763622283936s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.21939492225646973s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.21544551849365234s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.4006500244140625s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.3991694450378418s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 87.38433170318604s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.17943072319030762s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.32761049270629883s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.38258934020996094s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 43.27181577682495s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.237004280090332s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.598385810852051s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.21280455589294434s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 21.85925054550171s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.61241602897644s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 54.079787254333496s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.6591205596923828s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 23.158334732055664s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8713886737823486s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.22263836860656738s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 1.3105664253234863s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 13.334209680557251s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.8053722381591797s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.020975589752197266s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014519691467285156s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.9073486328125e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 7.3909759521484375e-06s
INFO | --- Analysis for data-bnf-fr took 696.8503429889679s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 5.316734313964844e-05s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.2737128734588623s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 8.082389831542969e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 1.2636184692382812e-05s
INFO | --- Analysis for data-cnr-it took 3.276174783706665s
Availability | SPARQL endpoint availability check for Data.gov took 4.410743713378906e-05s
Availability | VoID file availability check for Data.gov took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Data.gov took 0.2728240489959717s
Reputation | Calculation of the PageRank for Data.gov took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0008192062377929688s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.504753112792969e-05s
Believability | Calculation of trust value for Data.gov took 8.58306884765625e-06s
INFO | --- Analysis for data-gov took 2.8892834186553955s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 4.3392181396484375e-05s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.2739834785461426s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020638227462768555s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0010552406311035156s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 8.392333984375e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 8.106231689453125e-06s
INFO | --- Analysis for data-gov-ie took 2.8424859046936035s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.220008850097656e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2692999839782715s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.152557373046875e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 8.58306884765625e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.880949020385742s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 15.687281131744385s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.2680659294128418s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 5.888938903808594e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 5.9604644775390625e-06s
INFO | --- Analysis for data-hnm-hu took 48.68302798271179s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.13730669021606445s
Availability | VoID file availability check for Climb Dataincubator took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.7111320495605469s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.200241088867188e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.867813110351562e-06s
INFO | --- Analysis for data-incubator-climb took 3.393982172012329s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 4.124641418457031e-05s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.2714991569519043s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.412101745605469e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 6.198883056640625e-06s
INFO | --- Analysis for data-incubator-metoffice took 2.819227933883667s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.12712931632995605s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.25685787200927734s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020251750946044922s
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.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.821487426757812e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-moseley took 5.537478923797607s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.0541839599609375s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.28930020332336426s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.96453857421875e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.954939842224121s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.2633647918701172s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.320808410644531e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 7.867813110351562e-06s
INFO | --- Analysis for data-incubator-nasa took 2.811614751815796s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 4.220008850097656e-05s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.27296018600463867s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020395517349243164s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.462501525878906e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.8893649578094482s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 4.4345855712890625e-05s
Availability | VoID file availability check for Pokedex data in RDF took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.24786114692687988s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.560585021972656e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-pokedex took 2.86661434173584s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 4.3392181396484375e-05s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.26309657096862793s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007035732269287109s
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 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.8419601917266846s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 4.315376281738281e-05s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.2630927562713623s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.461143493652344e-05s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 6.9141387939453125e-06s
INFO | --- Analysis for data-open-ac-uk took 2.833080530166626s
Availability | SPARQL endpoint availability check for Persée in RDF took 4.291534423828125e-05s
Availability | VoID file availability check for Persée in RDF took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.2740917205810547s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010609626770019531s
Believability | Calculation of trust value for Persée in RDF took 7.867813110351562e-06s
INFO | --- Analysis for data-persee-fr took 2.933039426803589s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.1484832763671875e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.26309990882873535s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.02064681053161621s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.266334533691406e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 7.3909759521484375e-06s
INFO | --- Analysis for data-southampton-ac-uk took 2.7896320819854736s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.2194514274597168s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.26358890533447266s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00010967254638671875s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 6.4373016357421875e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 4.61799430847168s
Availability | SPARQL endpoint availability check for DataFAQs took 4.3392181396484375e-05s
Availability | VoID file availability check for DataFAQs took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.25983166694641113s
Reputation | Calculation of the PageRank for DataFAQs took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.170967102050781e-05s
Believability | Calculation of trust value for DataFAQs took 6.4373016357421875e-06s
INFO | --- Analysis for datafaqs took 2.8704612255096436s
Availability | SPARQL endpoint availability check for datahub took 4.3392181396484375e-05s
Availability | VoID file availability check for datahub took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for datahub took 0.26409912109375s
Reputation | Calculation of the PageRank for datahub took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for datahub took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for datahub took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for datahub took 4.7206878662109375e-05s
Believability | Calculation of trust value for datahub took 7.152557373046875e-06s
INFO | --- Analysis for datahub took 2.8377017974853516s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 5.984306335449219e-05s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.26125335693359375s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02031850814819336s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.794929504394531e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.2159347534179688e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 2.862291097640991s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.02464509010315s
Availability | VoID file availability check for datos-artium-org took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.27564501762390137s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020861387252807617s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011134147644042969s
Believability | Calculation of trust value for datos-artium-org took 7.3909759521484375e-06s
INFO | --- Analysis for datos-artium-org took 53.96944761276245s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 4.1484832763671875e-05s
Availability | VoID file availability check for Datos.bcn.cl took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.24324417114257812s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.2479248046875e-05s
Believability | Calculation of trust value for Datos.bcn.cl took 8.106231689453125e-06s
INFO | --- Analysis for datos-bcn-cl took 2.9099903106689453s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.30141663551330566s
Availability | VoID file availability check for datos.bne.es took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.2535843849182129s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00010967254638671875s
Believability | Calculation of trust value for datos.bne.es took 8.344650268554688e-06s
INFO | --- Analysis for datos-bne-es took 3.3873398303985596s
Availability | SPARQL endpoint availability check for DBkWik took 4.315376281738281e-05s
Availability | VoID file availability check for DBkWik took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for DBkWik took 0.2765343189239502s
Reputation | Calculation of the PageRank for DBkWik took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for DBkWik took 8.869171142578125e-05s
Believability | Calculation of trust value for DBkWik took 8.344650268554688e-06s
INFO | --- Analysis for dbkwik took 2.8658525943756104s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.1961669921875e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.292003870010376s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010442733764648438s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 2.857001304626465s
Availability | SPARQL endpoint availability check for dbnary took 4.38690185546875e-05s
Availability | VoID file availability check for dbnary took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for dbnary took 0.2755012512207031s
Reputation | Calculation of the PageRank for dbnary took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for dbnary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.4836273193359375e-05s
Believability | Calculation of trust value for dbnary took 8.106231689453125e-06s
INFO | --- Analysis for dbnary took 2.877495050430298s
Availability | SPARQL endpoint availability check for DBpedia took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for DBpedia took 0.26491785049438477s
Reputation | Calculation of the PageRank for DBpedia took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.000873565673828125s
Believability | Calculation of trust value for DBpedia took 7.62939453125e-06s
INFO | --- Analysis for dbpedia took 2.8930556774139404s
Availability | SPARQL endpoint availability check for DBpedia Commons took 4.220008850097656e-05s
Availability | VoID file availability check for DBpedia Commons took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.2661874294281006s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.771087646484375e-05s
Believability | Calculation of trust value for DBpedia Commons took 6.4373016357421875e-06s
INFO | --- Analysis for dbpedia-commons took 2.903428077697754s
Availability | SPARQL endpoint availability check for DBpedia in German took 4.2438507080078125e-05s
Availability | VoID file availability check for DBpedia in German took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.26669812202453613s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.437301635742188e-05s
Believability | Calculation of trust value for DBpedia in German took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-de took 2.8307254314422607s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 4.100799560546875e-05s
Availability | VoID file availability check for DBpedia in Greek took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.2557859420776367s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0009326934814453125s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00021004676818847656s
Believability | Calculation of trust value for DBpedia in Greek took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-el took 2.8405773639678955s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 5.7697296142578125e-05s
Availability | VoID file availability check for DBpedia in Spanish took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.2640695571899414s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010132789611816406s
Believability | Calculation of trust value for DBpedia in Spanish took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia-es took 2.870482921600342s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 4.363059997558594e-05s
Availability | VoID file availability check for DBpedia in Basque took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.26718783378601074s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.1948089599609375e-05s
Believability | Calculation of trust value for DBpedia in Basque took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia-eu took 2.863785982131958s
Availability | SPARQL endpoint availability check for DBpedia in French took 4.696846008300781e-05s
Availability | VoID file availability check for DBpedia in French took 0.0003476142883300781s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.28066205978393555s
Reputation | Calculation of the PageRank for DBpedia in French took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 8.96453857421875e-05s
Believability | Calculation of trust value for DBpedia in French took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-fr took 2.9054160118103027s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 4.172325134277344e-05s
Availability | VoID file availability check for DBpedia in Japanese took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.24480295181274414s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 9.655952453613281e-05s
Believability | Calculation of trust value for DBpedia in Japanese took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-ja took 2.7964274883270264s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.1484832763671875e-05s
Availability | VoID file availability check for dbpedia lite took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.23916077613830566s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.942054748535156e-05s
Believability | Calculation of trust value for dbpedia lite took 3.743171691894531e-05s
INFO | --- Analysis for dbpedia-lite took 2.828399658203125s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.315376281738281e-05s
Availability | VoID file availability check for DBpedia-Live took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.2651398181915283s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.0040740966796875e-05s
Believability | Calculation of trust value for DBpedia-Live took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-live took 2.8125147819519043s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 4.1484832763671875e-05s
Availability | VoID file availability check for DBpedia in Dutch took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2555544376373291s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001742839813232422s
Believability | Calculation of trust value for DBpedia in Dutch took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-nl took 2.849851131439209s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0003635883331298828s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.24619340896606445s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.606910705566406e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-pt took 2.7528321743011475s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.220008850097656e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.2688729763031006s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020586013793945312s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.123283386230469e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-spotlight took 2.7851979732513428s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.291534423828125e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.29009485244750977s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020748376846313477s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0008513927459716797s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 7.152557373046875e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 2.9140708446502686s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.3392181396484375e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.269545316696167s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.020991802215576172s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.2901763916015625e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 1.2874603271484375e-05s
INFO | --- Analysis for dbpedia-wikidata took 2.8483145236968994s
Availability | SPARQL endpoint availability check for DBpedia took 4.3392181396484375e-05s
Availability | VoID file availability check for DBpedia took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for DBpedia took 0.2525496482849121s
Reputation | Calculation of the PageRank for DBpedia took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.4332275390625e-05s
Believability | Calculation of trust value for DBpedia took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia_ took 2.8614747524261475s
Availability | SPARQL endpoint availability check for DBTropes took 4.7206878662109375e-05s
Availability | VoID file availability check for DBTropes took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for DBTropes took 0.2609531879425049s
Reputation | Calculation of the PageRank for DBTropes took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.703636169433594e-05s
Believability | Calculation of trust value for DBTropes took 7.867813110351562e-06s
INFO | --- Analysis for dbtropes took 3.061455488204956s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 7.534027099609375e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.2351241111755371s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.02096271514892578s
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.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.9577484130859375e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune took 2.8234407901763916s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.696846008300781e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0003082752227783203s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2733733654022217s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.021665096282958984s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.7220458984375e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 7.62939453125e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 2.884631395339966s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.38690185546875e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.28963470458984375s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.361701965332031e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 2.8369905948638916s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 9.222927570343018s
Availability | VoID file availability check for DBTune.org/classical took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.27274012565612793s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020290374755859375s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.2479248046875e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-classical took 18.74875569343567s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.35759711265564s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.32904958724975586s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.677078247070312e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 6.4373016357421875e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 17.902575731277466s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.378118991851807s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2756798267364502s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.628036499023438e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 7.62939453125e-06s
INFO | --- Analysis for dbtune-magnatune took 17.909136056900024s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.375003337860107s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.2754485607147217s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010514259338378906s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-musicbrainz took 17.898776292800903s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.374027013778687s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2742781639099121s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.221366882324219e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-myspace took 17.89911437034607s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.2648496627807617s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.170967102050781e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 8.821487426757812e-06s
INFO | --- Analysis for dclg-openuplabs took 2.881251096725464s
Availability | SPARQL endpoint availability check for data.dcs took 4.220008850097656e-05s
Availability | VoID file availability check for data.dcs took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for data.dcs took 0.23706626892089844s
Reputation | Calculation of the PageRank for data.dcs took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.67572021484375e-05s
Believability | Calculation of trust value for data.dcs took 6.9141387939453125e-06s
INFO | --- Analysis for dcs-sheffield took 2.7295186519622803s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.172325134277344e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.255786657333374s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.02086329460144043s
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.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.218650817871094e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 8.821487426757812e-06s
INFO | --- Analysis for de-budget took 2.849809408187866s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 7.43865966796875e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.26642608642578125s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.7670135498046875e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.3909759521484375e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 2.8271830081939697s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.363059997558594e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.2514326572418213s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.410743713378906e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 8.106231689453125e-06s
INFO | --- Analysis for debian-package-tracking-system took 2.865516185760498s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.0531158447265625e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.26499104499816895s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 2.8371810913085938e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.62939453125e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.834425926208496s
Availability | SPARQL endpoint availability check for Demografie took 4.3392181396484375e-05s
Availability | VoID file availability check for Demografie took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for Demografie took 0.2653167247772217s
Reputation | Calculation of the PageRank for Demografie took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Demografie took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.0517578125e-05s
Believability | Calculation of trust value for Demografie took 6.67572021484375e-06s
INFO | --- Analysis for demografie took 2.827902317047119s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 6.961822509765625e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.265669584274292s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020550251007080078s
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.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.703636169433594e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 7.152557373046875e-06s
INFO | --- Analysis for deustoentrepreneurship took 2.8280231952667236s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.124641418457031e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0002994537353515625s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.2685103416442871s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020335912704467773s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010204315185546875s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.2159347534179688e-05s
INFO | --- Analysis for deustotech took 2.8236865997314453s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.4392979145050049s
Availability | VoID file availability check for Deutsche Biographie took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.25261831283569336s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02071070671081543s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.00543212890625e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.1444091796875e-05s
INFO | --- Analysis for deutsche-biographie took 4.620218276977539s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.76837158203125e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2612175941467285s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.340576171875e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 7.152557373046875e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 2.8303496837615967s
Availability | SPARQL endpoint availability check for dev8d took 4.6253204345703125e-05s
Availability | VoID file availability check for dev8d took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for dev8d took 0.25063037872314453s
Reputation | Calculation of the PageRank for dev8d took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.772445678710938e-05s
Believability | Calculation of trust value for dev8d took 7.867813110351562e-06s
INFO | --- Analysis for dev8d took 2.8004860877990723s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 4.2438507080078125e-05s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.2770662307739258s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.021208524703979492s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0009529590606689453s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 6.127357482910156e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 9.5367431640625e-06s
INFO | --- Analysis for dewey_decimal_classification took 2.8035590648651123s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.2438507080078125e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.2836289405822754s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020725011825561523s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0009706020355224609s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.504753112792969e-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.8271708488464355s
Availability | SPARQL endpoint availability check for Diavgeia took 4.2438507080078125e-05s
Availability | VoID file availability check for Diavgeia took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.2665097713470459s
Reputation | Calculation of the PageRank for Diavgeia took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.130073547363281e-05s
Believability | Calculation of trust value for Diavgeia took 1.239776611328125e-05s
INFO | --- Analysis for diavgeia took 2.7930455207824707s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.1961669921875e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.26164674758911133s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011420249938964844s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for didactalia took 2.897695779800415s
Availability | SPARQL endpoint availability check for diigo.feed took 4.1961669921875e-05s
Availability | VoID file availability check for diigo.feed took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.25116539001464844s
Reputation | Calculation of the PageRank for diigo.feed took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.9325485229492188e-05s
Believability | Calculation of trust value for diigo.feed took 7.867813110351562e-06s
INFO | --- Analysis for diigo-feed took 2.783642053604126s
Availability | SPARQL endpoint availability check for DisGeNET took 4.1961669921875e-05s
Availability | VoID file availability check for DisGeNET took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.25090670585632324s
Reputation | Calculation of the PageRank for DisGeNET took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015211105346679688s
Believability | Calculation of trust value for DisGeNET took 1.33514404296875e-05s
INFO | --- Analysis for disgenet took 2.8671865463256836s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 6.842613220214844e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.26505184173583984s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.956390380859375e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 7.152557373046875e-06s
INFO | --- Analysis for disk took 2.830254077911377s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.220008850097656e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.2663257122039795s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 2.8848648071289062e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 1.1444091796875e-05s
INFO | --- Analysis for distritos-zaragoza took 2.9025959968566895s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.172325134277344e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2597634792327881s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.266334533691406e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 7.867813110351562e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 2.860572576522827s
Availability | SPARQL endpoint availability check for DM2E took 4.57763671875e-05s
Availability | VoID file availability check for DM2E took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for DM2E took 0.262209415435791s
Reputation | Calculation of the PageRank for DM2E took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for DM2E took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00012445449829101562s
Believability | Calculation of trust value for DM2E took 6.9141387939453125e-06s
INFO | --- Analysis for dm2e took 3.450465202331543s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.220008850097656e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.27434444427490234s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02024245262145996s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 2.9325485229492188e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 6.9141387939453125e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.8919904232025146s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 5.14984130859375e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.2727205753326416s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001614093780517578s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.2159347534179688e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 2.8773999214172363s
Availability | SPARQL endpoint availability check for DOAP Store took 4.1484832763671875e-05s
Availability | VoID file availability check for DOAP Store took 0.00034356117248535156s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.23981046676635742s
Reputation | Calculation of the PageRank for DOAP Store took 0.020493745803833008s
Interlinking | Calculation of Degree of Connection for DOAP Store took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.0994415283203125e-05s
Believability | Calculation of trust value for DOAP Store took 7.152557373046875e-06s
INFO | --- Analysis for doap_store took 2.8569223880767822s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.267692565917969e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.25983667373657227s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.985664367675781e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 1.049041748046875e-05s
INFO | --- Analysis for doi took 2.9048070907592773s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 4.363059997558594e-05s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.27626609802246094s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.62396240234375e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.3113021850585938e-05s
INFO | --- Analysis for drug-data-hifm took 2.7621989250183105s
Availability | SPARQL endpoint availability check for dspace took 4.220008850097656e-05s
Availability | VoID file availability check for dspace took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for dspace took 0.25965046882629395s
Reputation | Calculation of the PageRank for dspace took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for dspace took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for dspace took 3.075599670410156e-05s
Believability | Calculation of trust value for dspace took 6.67572021484375e-06s
INFO | --- Analysis for dspace took 2.791968584060669s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.1961669921875e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.26485133171081543s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.075599670410156e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 8.344650268554688e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.875105142593384s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 4.124641418457031e-05s
Availability | VoID file availability check for MetaLex Document Server took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.26505017280578613s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 2.86102294921875e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.62939453125e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 2.9058234691619873s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.3733444213867188s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.26434779167175293s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.02041459083557129s
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.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.600120544433594e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.3909759521484375e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 7.12264347076416s
Availability | SPARQL endpoint availability check for DWS-Group took 4.1484832763671875e-05s
Availability | VoID file availability check for DWS-Group took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.2635226249694824s
Reputation | Calculation of the PageRank for DWS-Group took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010085105895996094s
Believability | Calculation of trust value for DWS-Group took 8.344650268554688e-06s
INFO | --- Analysis for dws-group took 2.862903356552124s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 7.128715515136719e-05s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2679126262664795s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011587142944335938s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-alaska took 2.8389759063720703s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 4.291534423828125e-05s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.2456655502319336s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.1975250244140625e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-cau took 2.8305156230926514s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 5.0067901611328125e-05s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.24040746688842773s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.866455078125e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.900444746017456s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 4.1484832763671875e-05s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2514016628265381s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.489059448242188e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.8409476280212402s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 5.650520324707031e-05s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.25266337394714355s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013017654418945312s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-dartmouth took 2.902799606323242s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 4.1484832763671875e-05s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.24402499198913574s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02083730697631836s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.535385131835938e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 2.8848648071289062e-05s
INFO | --- Analysis for eagle-i-famu took 2.8427724838256836s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 4.673004150390625e-05s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.26340818405151367s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012683868408203125s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-harvard took 2.8649978637695312s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 4.1961669921875e-05s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.000244140625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2765672206878662s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012874603271484375s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.828108787536621s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 4.1961669921875e-05s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.26120972633361816s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.318092346191406e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-howard took 2.844163656234741s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 4.2438507080078125e-05s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.23916316032409668s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020247936248779297s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.127357482910156e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.8217623233795166s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 4.172325134277344e-05s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.24842333793640137s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020933151245117188s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0008206367492675781s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00013017654418945312s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-jsu took 2.9054832458496094s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 4.1961669921875e-05s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0003905296325683594s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.25095105171203613s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.8623809814453125e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-meharry took 2.8935999870300293s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 4.076957702636719e-05s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2793264389038086s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.021170616149902344s
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.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010347366333007812s
Believability | Calculation of trust value for eagle-i @ Montana State University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-montana took 2.8178741931915283s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 4.482269287109375e-05s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.2558722496032715s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.72747802734375e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 8.821487426757812e-06s
INFO | --- Analysis for eagle-i-msm took 2.843160629272461s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 4.4345855712890625e-05s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2784292697906494s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00013184547424316406s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.9236629009246826s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 4.2438507080078125e-05s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2506561279296875s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.318092346191406e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-psm took 2.7853856086730957s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 4.100799560546875e-05s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.2604331970214844s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020177125930786133s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.175041198730469e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-tsu took 2.80985951423645s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 5.221366882324219e-05s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00040149688720703125s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2506136894226074s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.8018784523010254s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 5.817413330078125e-05s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.26694321632385254s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00012087821960449219s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-uccaribe took 2.8354849815368652s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 4.220008850097656e-05s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2502431869506836s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012350082397460938s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-upr took 2.842287302017212s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 4.1961669921875e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.2825801372528076s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.389617919921875e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 9.5367431640625e-06s
INFO | --- Analysis for eagle-i-utep took 2.823540210723877s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 4.172325134277344e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2484731674194336s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.05718994140625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-utsa took 2.8909213542938232s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 4.076957702636719e-05s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.26566028594970703s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020394086837768555s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 8.749961853027344e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 2.8434152603149414s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 4.220008850097656e-05s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2707991600036621s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.772445678710938e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-xula took 2.851181983947754s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 4.2438507080078125e-05s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.25089168548583984s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 9.751319885253906e-05s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for ecb-linked-data took 2.8653833866119385s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 6.771087646484375e-05s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.2559969425201416s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.528594970703125e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 7.62939453125e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 2.8357489109039307s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 2.392796516418457s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2588944435119629s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006964206695556641s
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.58306884765625e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.309665203094482s
Availability | SPARQL endpoint availability check for ECLAP took 20.46981644630432s
Availability | VoID file availability check for ECLAP took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for ECLAP took 0.264620304107666s
Reputation | Calculation of the PageRank for ECLAP took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.601478576660156e-05s
Believability | Calculation of trust value for ECLAP took 7.3909759521484375e-06s
INFO | --- Analysis for eclap took 53.372841358184814s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.9114227294921875e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.23854827880859375s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020984649658203125s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.5789947509765625e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 8.344650268554688e-06s
INFO | --- Analysis for ecs took 3.0058352947235107s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.172325134277344e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0003173351287841797s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.23729920387268066s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020734786987304688s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.1948089599609375e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 1.7404556274414062e-05s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.8580620288848877s
Availability | SPARQL endpoint availability check for Edublogs took 4.124641418457031e-05s
Availability | VoID file availability check for Edublogs took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Edublogs took 0.25055789947509766s
Reputation | Calculation of the PageRank for Edublogs took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010395050048828125s
Believability | Calculation of trust value for Edublogs took 7.3909759521484375e-06s
INFO | --- Analysis for edublogs took 2.969672203063965s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 4.220008850097656e-05s
Availability | VoID file availability check for education.data.gov.uk took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.25154924392700195s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0008075237274169922s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.202957153320312e-05s
Believability | Calculation of trust value for education.data.gov.uk took 7.3909759521484375e-06s
INFO | --- Analysis for education-data-gov-uk took 2.7758870124816895s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.220008850097656e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.25451159477233887s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.2901763916015625e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.152557373046875e-06s
INFO | --- Analysis for education-openuplabs took 2.826908826828003s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 7.295608520507812e-05s
Availability | VoID file availability check for Educational programs - SISVU took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.2661890983581543s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02036881446838379s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 4.8160552978515625e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.3828277587890625e-05s
INFO | --- Analysis for educationalprograms_sisvu took 2.864367961883545s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 4.220008850097656e-05s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.25179004669189453s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.62396240234375e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 8.821487426757812e-06s
INFO | --- Analysis for eea took 2.8014721870422363s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 4.887580871582031e-05s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.26450276374816895s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.221366882324219e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 7.867813110351562e-06s
INFO | --- Analysis for eea-rod took 2.9107303619384766s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 4.291534423828125e-05s
Availability | VoID file availability check for EEA Vocabularies took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.2657928466796875s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02106022834777832s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.153915405273438e-05s
Believability | Calculation of trust value for EEA Vocabularies took 6.9141387939453125e-06s
INFO | --- Analysis for eea-vocabularies took 2.8524563312530518s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 4.363059997558594e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.26029515266418457s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for ege-university-linked-open-data took 2.817538261413574s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 3.981590270996094e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2676520347595215s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010204315185546875s
Believability | Calculation of trust value for EIONET RDF Data took 8.106231689453125e-06s
INFO | --- Analysis for eionet-rdf took 2.81758189201355s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.1484832763671875e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.2521958351135254s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 3.0994415283203125e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.867813110351562e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 2.8511993885040283s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 4.220008850097656e-05s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.24541783332824707s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020246505737304688s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.176399230957031e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 7.867813110351562e-06s
INFO | --- Analysis for elviajero took 2.787824869155884s
Availability | SPARQL endpoint availability check for EMN took 4.029273986816406e-05s
Availability | VoID file availability check for EMN took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for EMN took 0.2745993137359619s
Reputation | Calculation of the PageRank for EMN took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for EMN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for EMN took 3.790855407714844e-05s
Believability | Calculation of trust value for EMN took 7.62939453125e-06s
INFO | --- Analysis for emn took 2.829824209213257s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 7.414817810058594e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.26099157333374023s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.245208740234375e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 6.67572021484375e-06s
INFO | --- Analysis for enakting-co2emission took 2.8303325176239014s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.23161983489990234s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.743171691894531e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for enakting-crime took 2.8560614585876465s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.482269287109375e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.23907780647277832s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.0207517147064209s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.029273986816406e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 1.239776611328125e-05s
INFO | --- Analysis for enakting-energy took 2.8323476314544678s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00032138824462890625s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.258028507232666s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 8.869171142578125e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for enakting-mortality took 2.831392288208008s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.26445841789245605s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.552436828613281e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 9.5367431640625e-06s
INFO | --- Analysis for enakting-nhs took 2.927161931991577s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.24600672721862793s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.2928924560546875e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 6.67572021484375e-06s
INFO | --- Analysis for enakting-population took 2.828890800476074s
Availability | SPARQL endpoint availability check for Enel Shops took 4.291534423828125e-05s
Availability | VoID file availability check for Enel Shops took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.2511720657348633s
Reputation | Calculation of the PageRank for Enel Shops took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for Enel Shops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.075599670410156e-05s
Believability | Calculation of trust value for Enel Shops took 1.2159347534179688e-05s
INFO | --- Analysis for enel-shops took 2.858924150466919s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.2438507080078125e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.25022292137145996s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 2.956390380859375e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 6.9141387939453125e-06s
INFO | --- Analysis for energy-efficiency took 2.8209877014160156s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 5.078315734863281e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.2545294761657715s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020704984664916992s
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.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.8694658279418945s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.24552369117736816s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02051234245300293s
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.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.457069396972656e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.8750412464141846s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.265064001083374s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.8383216857910156s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.410743713378906e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.2505054473876953s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020811080932617188s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0009937286376953125s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.4809112548828125e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.800269365310669s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.2633061408996582s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0008108615875244141s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.2901763916015625e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.7936851978302s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.25783205032348633s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.02022409439086914s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 2.9325485229492188e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.7280871868133545s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 3.9577484130859375e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.24680042266845703s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.7886223793029785s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.8005104064941406s
Availability | VoID file availability check for English Heritage Periods List took 0.0002918243408203125s
Extra | Recovery of all triples for English Heritage Periods List took 0.3589363098144531s
Performance | Total latancy measurement for English Heritage Periods List took 1.6477265357971191s
Amount of data | Number of triples check for English Heritage Periods List took 0.6592798233032227s
Versatility | Languages check for English Heritage Periods List took 0.2966272830963135s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.6763973236083984s
Security | Check HTTPS for English Heritage Periods List took 0.21044373512268066s
Interpretability | RDF structures check for English Heritage Periods List took 0.26988816261291504s
Versatility | Serialization formats check for English Heritage Periods List took 0.6092095375061035s
Availability | RDF dump link check for English Heritage Periods List took 0.3124961853027344s
License | MR license check for English Heritage Periods List took 0.503058671951294s
License | HR license check for English Heritage Periods List took 0.3532414436340332s
Amount of data | Number of property check for English Heritage Periods List took 0.3917713165283203s
Understandability | Number of label check for English Heritage Periods List took 0.5285718441009521s
Understandability | URI regex check for English Heritage Periods List took 0.6637222766876221s
Understandability | Vocabs check for English Heritage Periods List took 0.500063419342041s
Verifiability | Authors check for English Heritage Periods List took 0.5237596035003662s
Verifiability | Publishers check for English Heritage Periods List took 0.3970046043395996s
Performance | Throughput check for English Heritage Periods List took 13.140638828277588s
Amount of data | Check the number of entities for English Heritage Periods List took 7.152557373046875e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.3628377914428711s
Interlinking | sameAs chians check for English Heritage Periods List took 0.31838369369506836s
Interlinking | skos check for English Heritage Periods List took 0.33890604972839355s
Interlinking | skos check for English Heritage Periods List took 0.34729719161987305s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.4035608768463135s
Currency | Creation date check for English Heritage Periods List took 0.6402583122253418s
Currency | Modification date check for English Heritage Periods List took 0.7168538570404053s
Rep.Conc. | URIs length for English Heritage Periods List took 0.6796154975891113s
Interoperability | New vocabularies check for English Heritage Periods List took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.4790337085723877s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3155667781829834s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.31569385528564453s
Consistency | Disjoint class check for English Heritage Periods List took 0.3112318515777588s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3116621971130371s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6490488052368164s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001404285430908203s
Security | Sign check for English Heritage Periods List took 0.4013404846191406s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.24837279319763184s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.361701965332031e-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 8.344650268554688e-06s
INFO | --- Analysis for english-heritage-periods-list took 50.185706615448s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 4.267692565917969e-05s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.24982786178588867s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02050328254699707s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.4332275390625e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 7.867813110351562e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 2.821561098098755s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 4.6253204345703125e-05s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.25739312171936035s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.409385681152344e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 6.4373016357421875e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 2.826188802719116s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.2438507080078125e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0003237724304199219s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.2519195079803467s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.9577484130859375e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 1.0728836059570312e-05s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.8777031898498535s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.124641418457031e-05s
Availability | VoID file availability check for English Heritage Places took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.25572633743286133s
Reputation | Calculation of the PageRank for English Heritage Places took 0.021181583404541016s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0010221004486083984s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.62396240234375e-05s
Believability | Calculation of trust value for English Heritage Places took 7.62939453125e-06s
INFO | --- Analysis for englishheritage_places took 2.839906930923462s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 4.172325134277344e-05s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0003135204315185547s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.2591211795806885s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 0.00010895729064941406s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 8.344650268554688e-06s
INFO | --- Analysis for enipedia took 2.844957113265991s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.1484832763671875e-05s
Availability | VoID file availability check for Entrez Gene took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.25428032875061035s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02073383331298828s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.838539123535156e-05s
Believability | Calculation of trust value for Entrez Gene took 7.62939453125e-06s
INFO | --- Analysis for entrez_gene took 2.8129637241363525s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.935264587402344e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.2535407543182373s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.24249267578125e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 6.9141387939453125e-06s
INFO | --- Analysis for entrez_gene_extract took 2.787353038787842s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 4.482269287109375e-05s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.27480316162109375s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 4.887580871582031e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 8.344650268554688e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 2.821743965148926s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 4.458427429199219e-05s
Availability | VoID file availability check for environment.data.gov.uk took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.23836016654968262s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020765304565429688s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.839897155761719e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 1.33514404296875e-05s
INFO | --- Analysis for environment-data-gov-uk took 2.8155133724212646s
Availability | SPARQL endpoint availability check for EARTh took 4.1961669921875e-05s
Availability | VoID file availability check for EARTh took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for EARTh took 0.2379744052886963s
Reputation | Calculation of the PageRank for EARTh took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for EARTh took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.584426879882812e-05s
Believability | Calculation of trust value for EARTh took 6.9141387939453125e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 2.769113779067993s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.00543212890625e-05s
Availability | VoID file availability check for EPA-CDR took 0.00021457672119140625s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.2545895576477051s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.695487976074219e-05s
Believability | Calculation of trust value for EPA-CDR took 5.4836273193359375e-06s
INFO | --- Analysis for epa-cdr took 2.7730019092559814s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.220008850097656e-05s
Availability | VoID file availability check for EPA-FRS took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.2400681972503662s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.05718994140625e-05s
Believability | Calculation of trust value for EPA-FRS took 1.0967254638671875e-05s
INFO | --- Analysis for epa-frs took 2.8407881259918213s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.076957702636719e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.26088786125183105s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020892620086669922s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.4332275390625e-05s
Believability | Calculation of trust value for EPA-RCRA took 1.2874603271484375e-05s
INFO | --- Analysis for epa-rcra took 2.850337505340576s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.5299530029296875e-05s
Availability | VoID file availability check for EPA-SRS took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.23906731605529785s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.295608520507812e-05s
Believability | Calculation of trust value for EPA-SRS took 6.4373016357421875e-06s
INFO | --- Analysis for epa-srs took 2.842158555984497s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.291534423828125e-05s
Availability | VoID file availability check for EPA-TRI took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2667045593261719s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.457069396972656e-05s
Believability | Calculation of trust value for EPA-TRI took 7.3909759521484375e-06s
INFO | --- Analysis for epa-tri took 2.899156093597412s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 3.981590270996094e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.24891233444213867s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.152557373046875e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 1.33514404296875e-05s
INFO | --- Analysis for epo took 2.8173632621765137s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 4.1484832763671875e-05s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.2686898708343506s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020772218704223633s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00012636184692382812s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.8687477111816406s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 4.1484832763671875e-05s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.24771833419799805s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 7.867813110351562e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 5.7220458984375e-06s
INFO | --- Analysis for eprtr took 2.800679922103882s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 4.172325134277344e-05s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2584841251373291s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.123283386230469e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 5.9604644775390625e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.829120635986328s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.1484832763671875e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.274245023727417s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.96453857421875e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 6.67572021484375e-06s
INFO | --- Analysis for esd-standards took 2.8939521312713623s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.363059997558594e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.27999258041381836s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.104873657226562e-05s
Believability | Calculation of trust value for ESD-Toolkit took 7.62939453125e-06s
INFO | --- Analysis for esd-toolkit took 2.856351613998413s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 4.220008850097656e-05s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0003757476806640625s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.24486494064331055s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020358562469482422s
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.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.009506225585938e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 8.106231689453125e-06s
INFO | --- Analysis for eu-agencies-bodies took 2.804426670074463s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 5.91278076171875e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.2500782012939453s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.0517578125e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 8.106231689453125e-06s
INFO | --- Analysis for eu-dgt-tm took 2.7752718925476074s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.124641418457031e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.25284242630004883s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.271766662597656e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 7.62939453125e-06s
INFO | --- Analysis for eu-institutions took 2.814438581466675s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 4.4345855712890625e-05s
Availability | VoID file availability check for EU Parliament Media Library took 0.0003063678741455078s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.25867676734924316s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02059626579284668s
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.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.3855438232421875e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 7.3909759521484375e-06s
INFO | --- Analysis for eu-parliament-media took 2.8651015758514404s
Availability | SPARQL endpoint availability check for EU Who Is Who took 4.100799560546875e-05s
Availability | VoID file availability check for EU Who Is Who took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2582969665527344s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.743171691894531e-05s
Believability | Calculation of trust value for EU Who Is Who took 6.9141387939453125e-06s
INFO | --- Analysis for eu-who-is-who took 2.8656649589538574s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 4.220008850097656e-05s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.24869346618652344s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.0531158447265625e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 6.4373016357421875e-06s
INFO | --- Analysis for eumida-linked-data took 2.8026626110076904s
Availability | SPARQL endpoint availability check for European Nature Information System took 4.2438507080078125e-05s
Availability | VoID file availability check for European Nature Information System took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.253495454788208s
Reputation | Calculation of the PageRank for European Nature Information System took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010442733764648438s
Believability | Calculation of trust value for European Nature Information System took 1.239776611328125e-05s
INFO | --- Analysis for eunis took 2.9071905612945557s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 4.792213439941406e-05s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.24882125854492188s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 6.937980651855469e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for eur-lex-rdf took 2.7883665561676025s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 4.172325134277344e-05s
Availability | VoID file availability check for Standard Eurobarometer took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.25226879119873047s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.3392181396484375e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 6.9141387939453125e-06s
INFO | --- Analysis for eurobarometer-standard took 2.7367653846740723s
Availability | SPARQL endpoint availability check for European Election Results took 4.291534423828125e-05s
Availability | VoID file availability check for European Election Results took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for European Election Results took 0.25868701934814453s
Reputation | Calculation of the PageRank for European Election Results took 0.02070331573486328s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.62396240234375e-05s
Believability | Calculation of trust value for European Election Results took 6.9141387939453125e-06s
INFO | --- Analysis for european-election-results took 2.768494129180908s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.100799560546875e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.2680206298828125s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for europeana-lod took 2.825200080871582s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.9114227294921875e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.2510974407196045s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02175283432006836s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.822845458984375e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.62939453125e-06s
INFO | --- Analysis for europeana-lod-v1 took 2.8184404373168945s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.029537677764892578s
Availability | VoID file availability check for Europeana SPARQL took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.2537260055541992s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.887580871582031e-05s
Believability | Calculation of trust value for Europeana SPARQL took 7.152557373046875e-06s
INFO | --- Analysis for europeana-sparql took 2.8806710243225098s
Availability | SPARQL endpoint availability check for EuroSentiment took 4.076957702636719e-05s
Availability | VoID file availability check for EuroSentiment took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.26429224014282227s
Reputation | Calculation of the PageRank for EuroSentiment took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.981590270996094e-05s
Believability | Calculation of trust value for EuroSentiment took 6.67572021484375e-06s
INFO | --- Analysis for eurosentiment took 2.8081071376800537s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 5.555152893066406e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.25987696647644043s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.700920104980469e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.9604644775390625e-06s
INFO | --- Analysis for eurostat-rdf took 2.8696136474609375s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.076957702636719e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.27371692657470703s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.029273986816406e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 7.62939453125e-06s
INFO | --- Analysis for eurovoc-in-skos took 2.8651187419891357s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.100799560546875e-05s
Availability | VoID file availability check for European Television Heritage took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.24562788009643555s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.52587890625e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 3.170967102050781e-05s
Believability | Calculation of trust value for European Television Heritage took 7.152557373046875e-06s
INFO | --- Analysis for euscreen took 2.7828710079193115s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.291534423828125e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2682976722717285s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.935264587402344e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 6.198883056640625e-06s
INFO | --- Analysis for euskadi-farmacias took 2.7984912395477295s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 4.1961669921875e-05s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2787172794342041s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.033348083496094e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 7.152557373046875e-06s
INFO | --- Analysis for eutc-productions took 2.891728639602661s
Availability | SPARQL endpoint availability check for EventMedia took 0.3090486526489258s
Availability | VoID file availability check for EventMedia took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for EventMedia took 0.25588560104370117s
Reputation | Calculation of the PageRank for EventMedia took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010895729064941406s
Believability | Calculation of trust value for EventMedia took 1.239776611328125e-05s
INFO | --- Analysis for event-media took 3.3635385036468506s
Availability | SPARQL endpoint availability check for Eventseer took 4.315376281738281e-05s
Availability | VoID file availability check for Eventseer took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for Eventseer took 0.26647138595581055s
Reputation | Calculation of the PageRank for Eventseer took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.744529724121094e-05s
Believability | Calculation of trust value for Eventseer took 7.867813110351562e-06s
INFO | --- Analysis for eventseer took 2.8612468242645264s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.172325134277344e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.2363572120666504s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020827770233154297s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 3.218650817871094e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 7.152557373046875e-06s
INFO | --- Analysis for facebook-lids took 2.938567876815796s
Availability | SPARQL endpoint availability check for Fact Forge took 5.698204040527344e-05s
Availability | VoID file availability check for Fact Forge took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.25530004501342773s
Reputation | Calculation of the PageRank for Fact Forge took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.147125244140625e-05s
Believability | Calculation of trust value for Fact Forge took 7.152557373046875e-06s
INFO | --- Analysis for fact-forge took 2.9121272563934326s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.38690185546875e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.2557711601257324s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.584426879882812e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 8.821487426757812e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 2.8244729042053223s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 4.267692565917969e-05s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.2672107219696045s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020787954330444336s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010967254638671875s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.33514404296875e-05s
INFO | --- Analysis for fao-linked-data took 2.888032913208008s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 4.291534423828125e-05s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2509903907775879s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.410743713378906e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 7.867813110351562e-06s
INFO | --- Analysis for farmbio-chembl took 2.8412699699401855s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.57763671875e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.2498641014099121s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.147125244140625e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 6.4373016357421875e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 2.795499563217163s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 7.152557373046875e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.26646924018859863s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020211458206176758s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 8.344650268554688e-06s
INFO | --- Analysis for farolapp-dataset took 2.888324022293091s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.267692565917969e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.2679727077484131s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0006999969482421875s
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 6.9141387939453125e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.8366539478302s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 5.364418029785156e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.26529431343078613s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 2.86102294921875e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 7.867813110351562e-06s
INFO | --- Analysis for federal-economic-rdf took 2.872776508331299s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.1484832763671875e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.263979434967041s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.0040740966796875e-05s
Believability | Calculation of trust value for Feed Wrapper took 1.1682510375976562e-05s
INFO | --- Analysis for feedwrapper-lids took 2.906046152114868s
Availability | SPARQL endpoint availability check for FiESTA took 4.172325134277344e-05s
Availability | VoID file availability check for FiESTA took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for FiESTA took 0.2545433044433594s
Reputation | Calculation of the PageRank for FiESTA took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for FiESTA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.933906555175781e-05s
Believability | Calculation of trust value for FiESTA took 7.152557373046875e-06s
INFO | --- Analysis for fiesta took 2.8321897983551025s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 6.771087646484375e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2653498649597168s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.033348083496094e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 7.62939453125e-06s
INFO | --- Analysis for finnish-municipalities took 2.8803870677948s
Availability | SPARQL endpoint availability check for firmao took 4.100799560546875e-05s
Availability | VoID file availability check for firmao took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for firmao took 0.2892467975616455s
Reputation | Calculation of the PageRank for firmao took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for firmao took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for firmao took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for firmao took 2.9087066650390625e-05s
Believability | Calculation of trust value for firmao took 7.152557373046875e-06s
INFO | --- Analysis for firmao took 2.9282913208007812s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.24752140045166016s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.779623508453369s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.076957702636719e-05s
Availability | VoID file availability check for Fishes of Texas took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2647969722747803s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02035355567932129s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.034706115722656e-05s
Believability | Calculation of trust value for Fishes of Texas took 6.9141387939453125e-06s
INFO | --- Analysis for fishes-of-texas took 2.772228479385376s
Availability | SPARQL endpoint availability check for flickr? wrappr took 5.364418029785156e-05s
Availability | VoID file availability check for flickr? wrappr took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.24183034896850586s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020239591598510742s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.202957153320312e-05s
Believability | Calculation of trust value for flickr? wrappr took 9.775161743164062e-06s
INFO | --- Analysis for flickr-wrappr took 2.6942577362060547s
Availability | SPARQL endpoint availability check for flickr.person took 4.220008850097656e-05s
Availability | VoID file availability check for flickr.person took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for flickr.person took 0.2814948558807373s
Reputation | Calculation of the PageRank for flickr.person took 0.020192623138427734s
Interlinking | Calculation of Degree of Connection for flickr.person took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for flickr.person took 2.8371810913085938e-05s
Believability | Calculation of trust value for flickr.person took 1.2159347534179688e-05s
INFO | --- Analysis for flickr_person took 2.8523828983306885s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.220008850097656e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.2466716766357422s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 2.7894973754882812e-05s
Believability | Calculation of trust value for flickr.videoobject took 6.9141387939453125e-06s
INFO | --- Analysis for flickr_videoobject took 2.7686007022857666s
Availability | SPARQL endpoint availability check for Fly-TED took 4.100799560546875e-05s
Availability | VoID file availability check for Fly-TED took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.28310203552246094s
Reputation | Calculation of the PageRank for Fly-TED took 0.021781206130981445s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.266334533691406e-05s
Believability | Calculation of trust value for Fly-TED took 7.62939453125e-06s
INFO | --- Analysis for fly-ted took 2.845536947250366s
Availability | SPARQL endpoint availability check for FlyAtlas took 4.0531158447265625e-05s
Availability | VoID file availability check for FlyAtlas took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.2575833797454834s
Reputation | Calculation of the PageRank for FlyAtlas took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.0040740966796875e-05s
Believability | Calculation of trust value for FlyAtlas took 8.58306884765625e-06s
INFO | --- Analysis for flyatlas took 2.8505825996398926s
Availability | SPARQL endpoint availability check for Flybase took 4.6253204345703125e-05s
Availability | VoID file availability check for Flybase took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for Flybase took 0.2890775203704834s
Reputation | Calculation of the PageRank for Flybase took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Flybase took 4.5299530029296875e-05s
Believability | Calculation of trust value for Flybase took 8.106231689453125e-06s
INFO | --- Analysis for flybase took 2.857556104660034s
Availability | SPARQL endpoint availability check for Flyted took 4.3392181396484375e-05s
Availability | VoID file availability check for Flyted took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Flyted took 0.24993085861206055s
Reputation | Calculation of the PageRank for Flyted took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Flyted took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Flyted took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.0279159545898438e-05s
Believability | Calculation of trust value for Flyted took 8.344650268554688e-06s
INFO | --- Analysis for flyted took 2.7847821712493896s
Availability | SPARQL endpoint availability check for Foodista took 4.1961669921875e-05s
Availability | VoID file availability check for Foodista took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Foodista took 0.27815699577331543s
Reputation | Calculation of the PageRank for Foodista took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.075599670410156e-05s
Believability | Calculation of trust value for Foodista took 1.3589859008789062e-05s
INFO | --- Analysis for foodista took 2.892457962036133s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 5.650520324707031e-05s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2352924346923828s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.224082946777344e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.867813110351562e-06s
INFO | --- Analysis for foodpedia took 2.8733959197998047s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.100799560546875e-05s
Availability | VoID file availability check for FORGE Course information took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.2554512023925781s
Reputation | Calculation of the PageRank for FORGE Course information took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.2901763916015625e-05s
Believability | Calculation of trust value for FORGE Course information took 1.239776611328125e-05s
INFO | --- Analysis for forge-course-information took 2.8193256855010986s
Availability | SPARQL endpoint availability check for FrameNet took 4.2438507080078125e-05s
Availability | VoID file availability check for FrameNet took 0.0003764629364013672s
Completeness | Calculation of interlinking completeness for FrameNet took 0.24905848503112793s
Reputation | Calculation of the PageRank for FrameNet took 0.020920753479003906s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.266334533691406e-05s
Believability | Calculation of trust value for FrameNet took 6.4373016357421875e-06s
INFO | --- Analysis for framenet took 2.8727216720581055s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 4.649162292480469e-05s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.35306358337402344s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.845329284667969e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for frb-linked-data took 2.936826229095459s
Availability | SPARQL endpoint availability check for Freebase took 4.220008850097656e-05s
Availability | VoID file availability check for Freebase took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Freebase took 0.23953795433044434s
Reputation | Calculation of the PageRank for Freebase took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.0002658367156982422s
Believability | Calculation of trust value for Freebase took 5.9604644775390625e-06s
INFO | --- Analysis for freebase took 2.8345937728881836s
Availability | SPARQL endpoint availability check for French School Program took 4.1961669921875e-05s
Availability | VoID file availability check for French School Program took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for French School Program took 0.2636711597442627s
Reputation | Calculation of the PageRank for French School Program took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for French School Program took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.147125244140625e-05s
Believability | Calculation of trust value for French School Program took 7.62939453125e-06s
INFO | --- Analysis for french-school-program took 2.8692984580993652s
Availability | SPARQL endpoint availability check for French School System took 8.082389831542969e-05s
Availability | VoID file availability check for French School System took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for French School System took 0.2644944190979004s
Reputation | Calculation of the PageRank for French School System took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for French School System took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for French School System took 3.170967102050781e-05s
Believability | Calculation of trust value for French School System took 6.9141387939453125e-06s
INFO | --- Analysis for french-school-system took 2.8945586681365967s
Availability | SPARQL endpoint availability check for French TimeBank took 4.482269287109375e-05s
Availability | VoID file availability check for French TimeBank took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.25888490676879883s
Reputation | Calculation of the PageRank for French TimeBank took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.0994415283203125e-05s
Believability | Calculation of trust value for French TimeBank took 5.9604644775390625e-06s
INFO | --- Analysis for french-timebank took 2.876965045928955s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 4.220008850097656e-05s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.24386215209960938s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.534027099609375e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-cordis took 2.8071277141571045s
Availability | SPARQL endpoint availability check for DailyMed took 4.124641418457031e-05s
Availability | VoID file availability check for DailyMed took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for DailyMed took 0.26559925079345703s
Reputation | Calculation of the PageRank for DailyMed took 0.020717144012451172s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00010251998901367188s
Believability | Calculation of trust value for DailyMed took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-dailymed took 2.90104079246521s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 4.1484832763671875e-05s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.000274658203125s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.25229620933532715s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.630752563476562e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-dblp took 2.861112356185913s
Availability | SPARQL endpoint availability check for Diseasome took 4.220008850097656e-05s
Availability | VoID file availability check for Diseasome took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Diseasome took 0.25130558013916016s
Reputation | Calculation of the PageRank for Diseasome took 0.02066349983215332s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010824203491210938s
Believability | Calculation of trust value for Diseasome took 6.4373016357421875e-06s
INFO | --- Analysis for fu-berlin-diseasome took 2.8684897422790527s
Availability | SPARQL endpoint availability check for DrugBank took 4.5299530029296875e-05s
Availability | VoID file availability check for DrugBank took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for DrugBank took 0.24912047386169434s
Reputation | Calculation of the PageRank for DrugBank took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for DrugBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DrugBank took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011134147644042969s
Believability | Calculation of trust value for DrugBank took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-drugbank took 2.8324811458587646s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 4.172325134277344e-05s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2543153762817383s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020689010620117188s
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.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.075599670410156e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 2.984074354171753s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 4.315376281738281e-05s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.286210298538208s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.0203397274017334s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.2479248046875e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 2.9344875812530518s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 4.315376281738281e-05s
Availability | VoID file availability check for European Employment Services (EURES) took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2638120651245117s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020930767059326172s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.843971252441406e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-eures took 2.847093105316162s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 4.172325134277344e-05s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.27910923957824707s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.021430492401123047s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 0.0001049041748046875s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-eurostat took 2.9310696125030518s
Availability | SPARQL endpoint availability check for MediCare took 5.5789947509765625e-05s
Availability | VoID file availability check for MediCare took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for MediCare took 0.2657449245452881s
Reputation | Calculation of the PageRank for MediCare took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for MediCare took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for MediCare took 5.626678466796875e-05s
Believability | Calculation of trust value for MediCare took 7.867813110351562e-06s
INFO | --- Analysis for fu-berlin-medicare took 2.8168227672576904s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 4.220008850097656e-05s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0003132820129394531s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.2574748992919922s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.653236389160156e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 8.58306884765625e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 2.9065299034118652s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 4.267692565917969e-05s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.2710909843444824s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.298324584960938e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-sider took 2.8743131160736084s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 7.653236389160156e-05s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2885556221008301s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020885467529296875s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.62939453125e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 8.58306884765625e-06s
INFO | --- Analysis for fu-berlin-stitch took 2.8458714485168457s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.2438507080078125e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.24840378761291504s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.4332275390625e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 6.4373016357421875e-06s
INFO | --- Analysis for galen_from_co-odeorg took 2.798445224761963s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.291534423828125e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.26587700843811035s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.172325134277344e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 8.106231689453125e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 2.7951302528381348s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.220008850097656e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.25994229316711426s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.021026611328125s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010442733764648438s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.2874603271484375e-05s
INFO | --- Analysis for garnicaplywood took 2.829216718673706s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.2438507080078125e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.25050997734069824s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02080249786376953s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.584426879882812e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.62939453125e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 2.840230941772461s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 4.3392181396484375e-05s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.25521254539489746s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.250640869140625e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for gemet took 2.836207628250122s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.1484832763671875e-05s
Availability | VoID file availability check for gemet-annotated took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.27883100509643555s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.361701965332031e-05s
Believability | Calculation of trust value for gemet-annotated took 7.152557373046875e-06s
INFO | --- Analysis for gemet-annotated took 2.8467400074005127s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 4.38690185546875e-05s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2573354244232178s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020418167114257812s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 7.62939453125e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 2.8151133060455322s
Availability | SPARQL endpoint availability check for geo.place took 4.267692565917969e-05s
Availability | VoID file availability check for geo.place took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for geo.place took 0.25844621658325195s
Reputation | Calculation of the PageRank for geo.place took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for geo.place took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for geo.place took 2.8371810913085938e-05s
Believability | Calculation of trust value for geo.place took 6.67572021484375e-06s
INFO | --- Analysis for geo_place took 2.841151475906372s
Availability | SPARQL endpoint availability check for geodomainwn took 4.100799560546875e-05s
Availability | VoID file availability check for geodomainwn took 0.0003185272216796875s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.27060866355895996s
Reputation | Calculation of the PageRank for geodomainwn took 0.02792978286743164s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0013899803161621094s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 6.651878356933594e-05s
Believability | Calculation of trust value for geodomainwn took 1.2874603271484375e-05s
INFO | --- Analysis for geodomainwn took 2.872621774673462s
Availability | SPARQL endpoint availability check for GeoEcuador took 5.53131103515625e-05s
Availability | VoID file availability check for GeoEcuador took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.23779749870300293s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GeoEcuador took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.318092346191406e-05s
Believability | Calculation of trust value for GeoEcuador took 7.3909759521484375e-06s
INFO | --- Analysis for geoecuador took 2.7987120151519775s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2685532569885254s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.24171853065490723s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020381927490234375s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.794929504394531e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 8.344650268554688e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 7.531581878662109s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.291534423828125e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.2571451663970947s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020374298095703125s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.0517578125e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 8.106231689453125e-06s
INFO | --- Analysis for geographic-openuplabs took 2.7675609588623047s
Availability | SPARQL endpoint availability check for GeoLinkedData took 4.3392181396484375e-05s
Availability | VoID file availability check for GeoLinkedData took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.2516040802001953s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.678436279296875e-05s
Believability | Calculation of trust value for GeoLinkedData took 7.62939453125e-06s
INFO | --- Analysis for geolinkeddata took 2.7277097702026367s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 5.7220458984375e-05s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.2548530101776123s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 7.915496826171875e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 2.750433921813965s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.982948303222656e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2378826141357422s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00046753883361816406s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.3909759521484375e-06s
INFO | --- Analysis for geonames-semantic-web took 2.7602405548095703s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 5.078315734863281e-05s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.00031304359436035156s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.2820010185241699s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.0001366138458251953s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for geospecies took 2.8048763275146484s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.100799560546875e-05s
Availability | VoID file availability check for GeoWordNet took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.26906442642211914s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.887580871582031e-05s
Believability | Calculation of trust value for GeoWordNet took 8.106231689453125e-06s
INFO | --- Analysis for geowordnet took 2.842200517654419s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 5.364418029785156e-05s
Availability | VoID file availability check for German labor law thesaurus took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.25461649894714355s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020867347717285156s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.796287536621094e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.62939453125e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.785263776779175s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.27421021461486816s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.076957702636719e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.2874603271484375e-05s
INFO | --- Analysis for germlex took 2.86698579788208s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 4.172325134277344e-05s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2745707035064697s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.988380432128906e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.106231689453125e-06s
INFO | --- Analysis for gesis-thesoz took 2.871786117553711s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.46451735496521s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.26511549949645996s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.021596431732177734s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 8.130073547363281e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for getty-aat took 8.108603954315186s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.3007962703704834s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.24263310432434082s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020795106887817383s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.53131103515625e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 8.106231689453125e-06s
INFO | --- Analysis for getty-tgn took 5.8853349685668945s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 4.220008850097656e-05s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.26131653785705566s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.021662473678588867s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.337860107421875e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 7.62939453125e-06s
INFO | --- Analysis for gipuzkoademografia took 2.842604637145996s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.458427429199219e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.23553752899169922s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.1948089599609375e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 7.62939453125e-06s
INFO | --- Analysis for glastonbury-2011 took 2.857548236846924s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.291534423828125e-05s
Availability | VoID file availability check for Global Change Information System took 0.0003712177276611328s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.24785518646240234s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020711898803710938s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.218650817871094e-05s
Believability | Calculation of trust value for Global Change Information System took 8.106231689453125e-06s
INFO | --- Analysis for global-change-information-system took 2.8817172050476074s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.076957702636719e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.26456618309020996s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.054473876953125e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 8.344650268554688e-06s
INFO | --- Analysis for global-hunger-index-2011 took 2.8820629119873047s
Availability | SPARQL endpoint availability check for Glottolog took 4.172325134277344e-05s
Availability | VoID file availability check for Glottolog took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2779817581176758s
Reputation | Calculation of the PageRank for Glottolog took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.340576171875e-05s
Believability | Calculation of trust value for Glottolog took 8.106231689453125e-06s
INFO | --- Analysis for glottolog took 2.819638729095459s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.267692565917969e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.26336002349853516s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 9.989738464355469e-05s
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 2.8627803325653076s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.315376281738281e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.24089288711547852s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.020445585250854492s
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.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.86102294921875e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 7.62939453125e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.7553977966308594s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.410743713378906e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.25978851318359375s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.02103590965270996s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.075599670410156e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.2159347534179688e-05s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.8961520195007324s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.291534423828125e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2592504024505615s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.364418029785156e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 7.62939453125e-06s
INFO | --- Analysis for gold took 2.9103455543518066s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.76837158203125e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.2591109275817871s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.723403930664062e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 7.3909759521484375e-06s
INFO | --- Analysis for googleart-wrapper took 2.883352518081665s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 4.172325134277344e-05s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2892458438873291s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02068305015563965s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 4.029273986816406e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 7.62939453125e-06s
INFO | --- Analysis for govagribus-denmark took 2.8588788509368896s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 4.5299530029296875e-05s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.24684548377990723s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.02081918716430664s
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.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 9.608268737792969e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 2.9178102016448975s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 4.315376281738281e-05s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.23509955406188965s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.916854858398438e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 1.239776611328125e-05s
INFO | --- Analysis for govtrack took 2.8849449157714844s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.38690185546875e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.266284704208374s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02037978172302246s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.365776062011719e-05s
Believability | Calculation of trust value for greek-administrative-geography took 8.106231689453125e-06s
INFO | --- Analysis for greek-administrative-geography took 2.8665008544921875s
Availability | SPARQL endpoint availability check for Greek Wordnet took 4.792213439941406e-05s
Availability | VoID file availability check for Greek Wordnet took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2895960807800293s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.0531158447265625e-05s
Believability | Calculation of trust value for Greek Wordnet took 8.58306884765625e-06s
INFO | --- Analysis for greek-wordnet took 2.913496971130371s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.1484832763671875e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.27909159660339355s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.021026611328125s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010228157043457031s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 8.344650268554688e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 2.884507417678833s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 4.220008850097656e-05s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.265362024307251s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.022142410278320312s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.935264587402344e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 6.9141387939453125e-06s
INFO | --- Analysis for grrp took 2.8465538024902344s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 4.1484832763671875e-05s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.25482964515686035s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.747245788574219e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 6.67572021484375e-06s
INFO | --- Analysis for grrt took 2.830441474914551s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.4345855712890625e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.26302433013916016s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.033348083496094e-05s
Believability | Calculation of trust value for Project Gutenberg took 8.106231689453125e-06s
INFO | --- Analysis for gutenberg took 3.6919350624084473s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.5299530029296875e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.2775712013244629s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.409385681152344e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.927586555480957s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 5.698204040527344e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.2801682949066162s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.02099132537841797s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.000823974609375s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 7.343292236328125e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 7.867813110351562e-06s
INFO | --- Analysis for heartfailure took 2.8333370685577393s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.714768886566162s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.24785995483398438s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02055191993713379s
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.1682510375976562e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.981590270996094e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 8.344650268554688e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 54.66464328765869s
Availability | SPARQL endpoint availability check for Hedatuz took 0.3567464351654053s
Availability | VoID file availability check for Hedatuz took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.2483997344970703s
Reputation | Calculation of the PageRank for Hedatuz took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.9577484130859375e-05s
Believability | Calculation of trust value for Hedatuz took 6.67572021484375e-06s
INFO | --- Analysis for hedatuz took 3.3495912551879883s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 4.2438507080078125e-05s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2504246234893799s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012302398681640625s
Believability | Calculation of trust value for Hellenic Fire Brigade took 7.867813110351562e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.815369129180908s
Availability | SPARQL endpoint availability check for Hellenic Police took 4.410743713378906e-05s
Availability | VoID file availability check for Hellenic Police took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.26734066009521484s
Reputation | Calculation of the PageRank for Hellenic Police took 0.021002769470214844s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0009610652923583984s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00015044212341308594s
Believability | Calculation of trust value for Hellenic Police took 7.152557373046875e-06s
INFO | --- Analysis for hellenic-police took 3.050405740737915s
Availability | SPARQL endpoint availability check for Homologene took 4.458427429199219e-05s
Availability | VoID file availability check for Homologene took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Homologene took 0.26300740242004395s
Reputation | Calculation of the PageRank for Homologene took 0.02043771743774414s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.0994415283203125e-05s
Believability | Calculation of trust value for Homologene took 6.198883056640625e-06s
INFO | --- Analysis for homologene took 2.858654022216797s
Availability | SPARQL endpoint availability check for Noticias Universia took 4.4345855712890625e-05s
Availability | VoID file availability check for Noticias Universia took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.29204416275024414s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 3.62396240234375e-05s
Believability | Calculation of trust value for Noticias Universia took 8.106231689453125e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 2.8027923107147217s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.291534423828125e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.27924633026123047s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.147125244140625e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 5.9604644775390625e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.8495750427246094s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.315376281738281e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.2666494846343994s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020505905151367188s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 2.956390380859375e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 1.1682510375976562e-05s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.817742347717285s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.1961669921875e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2835085391998291s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 2.956390380859375e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 8.106231689453125e-06s
INFO | --- Analysis for hud-library-usagedata took 2.8796019554138184s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.363867998123169s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.24971652030944824s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010514259338378906s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 7.867813110351562e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.542423248291016s
Availability | SPARQL endpoint availability check for IATE RDF took 4.315376281738281e-05s
Availability | VoID file availability check for IATE RDF took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.24381637573242188s
Reputation | Calculation of the PageRank for IATE RDF took 0.020803451538085938s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.790855407714844e-05s
Believability | Calculation of trust value for IATE RDF took 7.62939453125e-06s
INFO | --- Analysis for iate-rdf took 2.8857710361480713s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 4.267692565917969e-05s
Availability | VoID file availability check for IATI as Linked Data took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.23936700820922852s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.463859558105469e-05s
Believability | Calculation of trust value for IATI as Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for iati-as-linked-data took 2.8726842403411865s
Availability | SPARQL endpoint availability check for ICANE took 4.267692565917969e-05s
Availability | VoID file availability check for ICANE took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for ICANE took 0.24474406242370605s
Reputation | Calculation of the PageRank for ICANE took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for ICANE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.749961853027344e-05s
Believability | Calculation of trust value for ICANE took 9.298324584960938e-06s
INFO | --- Analysis for icane took 2.8220393657684326s
Availability | SPARQL endpoint availability check for ichoose took 4.1484832763671875e-05s
Availability | VoID file availability check for ichoose took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for ichoose took 0.23547935485839844s
Reputation | Calculation of the PageRank for ichoose took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for ichoose took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.604194641113281e-05s
Believability | Calculation of trust value for ichoose took 6.9141387939453125e-06s
INFO | --- Analysis for ichoose took 2.8343076705932617s
Availability | SPARQL endpoint availability check for Identifiers.org took 5.125999450683594e-05s
Availability | VoID file availability check for Identifiers.org took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.24495244026184082s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 4.4345855712890625e-05s
Believability | Calculation of trust value for Identifiers.org took 6.67572021484375e-06s
INFO | --- Analysis for identifiers-org took 2.812692642211914s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 5.459785461425781e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.25035858154296875s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0008106231689453125s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.724761962890625e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 6.9141387939453125e-06s
INFO | --- Analysis for idreffr took 2.7006568908691406s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 5.435943603515625e-05s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.2695918083190918s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.0067901611328125e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 7.867813110351562e-06s
INFO | --- Analysis for ids took 2.761575698852539s
Availability | SPARQL endpoint availability check for ietflang took 4.172325134277344e-05s
Availability | VoID file availability check for ietflang took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for ietflang took 0.2314291000366211s
Reputation | Calculation of the PageRank for ietflang took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for ietflang took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.6253204345703125e-05s
Believability | Calculation of trust value for ietflang took 5.4836273193359375e-06s
INFO | --- Analysis for ietflang took 2.797323226928711s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.8613407611846924s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.27558183670043945s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.0994415283203125e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 7.152557373046875e-06s
INFO | --- Analysis for iislod-test took 3.7443463802337646s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 4.172325134277344e-05s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.2534210681915283s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 8.869171142578125e-05s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 6.4373016357421875e-06s
INFO | --- Analysis for imagesnippets took 2.8175249099731445s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 5.364418029785156e-05s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.24767160415649414s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.487701416015625e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.5497207641601562e-05s
INFO | --- Analysis for imf-linked-data took 2.769287109375s
Availability | SPARQL endpoint availability check for IMGpedia took 4.2438507080078125e-05s
Availability | VoID file availability check for IMGpedia took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2292332649230957s
Reputation | Calculation of the PageRank for IMGpedia took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.123283386230469e-05s
Believability | Calculation of trust value for IMGpedia took 7.152557373046875e-06s
INFO | --- Analysis for imgpedia took 2.7329843044281006s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 7.104873657226562e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.23990821838378906s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 3.123283386230469e-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.827263832092285s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.2438507080078125e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.24040889739990234s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020473718643188477s
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.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 2.956390380859375e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 7.3909759521484375e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.7578608989715576s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.1484832763671875e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.25643444061279297s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 2.9802322387695312e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 6.9141387939453125e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.796522617340088s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.100799560546875e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.24997878074645996s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.0040740966796875e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 7.867813110351562e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.8685755729675293s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.2438507080078125e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.24604272842407227s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020859718322753906s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010228157043457031s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 6.9141387939453125e-06s
INFO | --- Analysis for ineverycrea took 2.869823694229126s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.315376281738281e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.26293349266052246s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020727872848510742s
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.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.083747863769531e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 7.62939453125e-06s
INFO | --- Analysis for ineverycrea-argentina took 2.8142378330230713s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for Influence Tracker Dataset took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.2595231533050537s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02056407928466797s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 6.604194641113281e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.867813110351562e-06s
INFO | --- Analysis for influence-tracker-dataset took 2.91363263130188s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.315376281738281e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.25005483627319336s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020820140838623047s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 4.029273986816406e-05s
Believability | Calculation of trust value for INSEMTIVES took 7.62939453125e-06s
INFO | --- Analysis for insemtives took 2.8631820678710938s
Availability | SPARQL endpoint availability check for instagram.person took 4.1484832763671875e-05s
Availability | VoID file availability check for instagram.person took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for instagram.person took 0.23593711853027344s
Reputation | Calculation of the PageRank for instagram.person took 0.023424386978149414s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for instagram.person took 4.315376281738281e-05s
Believability | Calculation of trust value for instagram.person took 7.152557373046875e-06s
INFO | --- Analysis for instagram_person took 2.854614734649658s
Availability | SPARQL endpoint availability check for instagram.videoobject took 5.745887756347656e-05s
Availability | VoID file availability check for instagram.videoobject took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.2619955539703369s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.0209505558013916s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 3.314018249511719e-05s
Believability | Calculation of trust value for instagram.videoobject took 1.1920928955078125e-05s
INFO | --- Analysis for instagram_videoobject took 2.864429235458374s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 5.4836273193359375e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2342681884765625s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub Countries took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-countries took 2.8244168758392334s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.220008850097656e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.273761510848999s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.1948089599609375e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.916062831878662s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.3392181396484375e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0003209114074707031s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.25981736183166504s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.218650817871094e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-organizations took 2.8499693870544434s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub People took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.29285693168640137s
Reputation | Calculation of the PageRank for Instance Hub People took 0.02073383331298828s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub People took 9.5367431640625e-06s
INFO | --- Analysis for instance-hub-people took 2.9834368228912354s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 7.271766662597656e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.24086785316467285s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020342111587524414s
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.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.843977212905884s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.8160552978515625e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0008251667022705078s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.25002217292785645s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.170967102050781e-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.8425488471984863s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.38690185546875e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2545650005340576s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.266334533691406e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.7993617057800293s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.220008850097656e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.24929571151733398s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020644187927246094s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.170967102050781e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.869936227798462s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.291534423828125e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2779579162597656s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.8860116004943848s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 7.700920104980469e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.27584266662597656s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.075599670410156e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.928734064102173s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.291534423828125e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.27643489837646484s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.218650817871094e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 1.239776611328125e-05s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.8557281494140625s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.315376281738281e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.2598404884338379s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020807504653930664s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.170967102050781e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.3909759521484375e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.8492701053619385s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.124641418457031e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.26891160011291504s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02095198631286621s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.5367431640625e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for interactivemaps-gnoss took 2.9056594371795654s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.4345855712890625e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2771430015563965s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.075599670410156e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 8.106231689453125e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.8417489528656006s
Availability | SPARQL endpoint availability check for intervalue took 4.267692565917969e-05s
Availability | VoID file availability check for intervalue took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for intervalue took 0.2638511657714844s
Reputation | Calculation of the PageRank for intervalue took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for intervalue took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.699562072753906e-05s
Believability | Calculation of trust value for intervalue took 8.821487426757812e-06s
INFO | --- Analysis for intervalue took 2.8377439975738525s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.601478576660156e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2752692699432373s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02129077911376953s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.696846008300781e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 8.106231689453125e-06s
INFO | --- Analysis for iptc-newscodes took 2.912675142288208s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.100799560546875e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.26775670051574707s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.02127361297607422s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.3855438232421875e-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.849801540374756s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 4.1961669921875e-05s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.2752358913421631s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020467758178710938s
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.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.751319885253906e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 9.059906005859375e-06s
INFO | --- Analysis for iserve took 2.841146469116211s
Availability | SPARQL endpoint availability check for ISIC V4 took 4.1961669921875e-05s
Availability | VoID file availability check for ISIC V4 took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2778196334838867s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.5762786865234375e-05s
Believability | Calculation of trust value for ISIC V4 took 7.867813110351562e-06s
INFO | --- Analysis for isic-v4 took 2.925788640975952s
Availability | SPARQL endpoint availability check for Isidore took 4.2438507080078125e-05s
Availability | VoID file availability check for Isidore took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Isidore took 0.2605292797088623s
Reputation | Calculation of the PageRank for Isidore took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for Isidore took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Isidore took 2.9087066650390625e-05s
Believability | Calculation of trust value for Isidore took 7.152557373046875e-06s
INFO | --- Analysis for isidore took 2.808340549468994s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 8.940696716308594e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.2568204402923584s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.170967102050781e-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.8254661560058594s
Availability | SPARQL endpoint availability check for ISOcat took 4.220008850097656e-05s
Availability | VoID file availability check for ISOcat took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for ISOcat took 0.24672269821166992s
Reputation | Calculation of the PageRank for ISOcat took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.031990051269531e-05s
Believability | Calculation of trust value for ISOcat took 7.867813110351562e-06s
INFO | --- Analysis for isocat took 2.8337595462799072s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.172325134277344e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.25000739097595215s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.719329833984375e-05s
Believability | Calculation of trust value for ISOcat-metadata took 8.106231689453125e-06s
INFO | --- Analysis for isocat-metadata took 2.887619733810425s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.315376281738281e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.25865983963012695s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.7670135498046875e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 1.0013580322265625e-05s
INFO | --- Analysis for ispra-lod-ihi took 2.8951008319854736s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.458427429199219e-05s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.26665568351745605s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.022539377212524414s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010347366333007812s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.0067901611328125e-06s
INFO | --- Analysis for ispra-lod-place took 2.8718504905700684s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.601478576660156e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2608187198638916s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.647804260253906e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 6.67572021484375e-06s
INFO | --- Analysis for ispra-lod-rmn took 2.799616575241089s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 4.291534423828125e-05s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.2676565647125244s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.528594970703125e-05s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-ron took 2.875575542449951s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.2438507080078125e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.2918698787689209s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.0209047794342041s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 2.956390380859375e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 7.867813110351562e-06s
INFO | --- Analysis for ispra-lod-sc took 2.881653070449829s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 4.172325134277344e-05s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.27384209632873535s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.021300315856933594s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.535385131835938e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 1.8596649169921875e-05s
INFO | --- Analysis for istat-immigration took 2.89490008354187s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.220008850097656e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.2762415409088135s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.02050924301147461s
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.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.0517578125e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 1.239776611328125e-05s
INFO | --- Analysis for istat-immigrazione took 2.935803174972534s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 5.364418029785156e-05s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2658512592315674s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020371198654174805s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.9325485229492188e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 7.3909759521484375e-06s
INFO | --- Analysis for it-aifa-drug-prices took 2.8378517627716064s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 4.1961669921875e-05s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2478795051574707s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.414817810058594e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.1205673217773438e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 2.8134968280792236s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.124641418457031e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.26137304306030273s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 2.9802322387695312e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 7.62939453125e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.8964803218841553s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.792213439941406e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.00032401084899902344s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.26846861839294434s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.021260499954223633s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0008833408355712891s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 4.458427429199219e-05s
Believability | Calculation of trust value for IWMI Research Reports took 8.344650268554688e-06s
INFO | --- Analysis for iwmi-research-reports took 2.8358795642852783s
Availability | SPARQL endpoint availability check for IWN took 4.1961669921875e-05s
Availability | VoID file availability check for IWN took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for IWN took 0.2606391906738281s
Reputation | Calculation of the PageRank for IWN took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for IWN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for IWN took 3.647804260253906e-05s
Believability | Calculation of trust value for IWN took 7.3909759521484375e-06s
INFO | --- Analysis for iwn took 2.7783069610595703s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.2438507080078125e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.26360535621643066s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.020314693450927734s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 2.9325485229492188e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 6.9141387939453125e-06s
INFO | --- Analysis for j-global-knowledge took 2.810314655303955s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.267692565917969e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.2563486099243164s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.021968841552734375s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 3.266334533691406e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 7.152557373046875e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.818833112716675s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.104370594024658s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.258770227432251s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.02060079574584961s
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.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.008148193359375e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 8.344650268554688e-06s
INFO | --- Analysis for jamendo-dbtune took 18.6068172454834s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.2438507080078125e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.22710561752319336s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.363059997558594e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for japan-radioactivity-stat took 2.7827956676483154s
Availability | SPARQL endpoint availability check for JEL Classification took 4.1484832763671875e-05s
Availability | VoID file availability check for JEL Classification took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2401103973388672s
Reputation | Calculation of the PageRank for JEL Classification took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for JEL Classification took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.075599670410156e-05s
Believability | Calculation of trust value for JEL Classification took 6.9141387939453125e-06s
INFO | --- Analysis for jel-classification took 2.798647403717041s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.0499863624572754s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2712850570678711s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02037978172302246s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 2.9087066650390625e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 6.67572021484375e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 4.036451816558838s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.928640127182s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.3097405433654785s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020726919174194336s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 6.937980651855469e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.7404556274414062e-05s
INFO | --- Analysis for jita took 536.7089352607727s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.220008850097656e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.6915678977966309s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.504753112792969e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 1.2636184692382812e-05s
INFO | --- Analysis for jmdict took 4.6358561515808105s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.073802947998047s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.24924731254577637s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02098703384399414s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.726119995117188e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.62939453125e-06s
INFO | --- Analysis for john-goodwins-family-tree took 22.916964292526245s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 4.124641418457031e-05s
Availability | VoID file availability check for JRC-Names-MLODE took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.2577800750732422s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.0205385684967041s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 7.224082946777344e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 8.344650268554688e-06s
INFO | --- Analysis for jrc-names-mlode took 2.78755521774292s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.291534423828125e-05s
Availability | VoID file availability check for JudaicaLink took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2601172924041748s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010061264038085938s
Believability | Calculation of trust value for JudaicaLink took 6.198883056640625e-06s
INFO | --- Analysis for judaicalink took 2.7905938625335693s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.076957702636719e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.2429521083831787s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.075599670410156e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 6.9141387939453125e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.8621883392333984s
Availability | SPARQL endpoint availability check for KAKEN took 4.267692565917969e-05s
Availability | VoID file availability check for KAKEN took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for KAKEN took 0.25998449325561523s
Reputation | Calculation of the PageRank for KAKEN took 0.020939350128173828s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for KAKEN took 4.00543212890625e-05s
Believability | Calculation of trust value for KAKEN took 1.1682510375976562e-05s
INFO | --- Analysis for kaken took 2.8296687602996826s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 4.076957702636719e-05s
Availability | VoID file availability check for Kallikratis municipalities took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.25937509536743164s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020586490631103516s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.179115295410156e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 7.867813110351562e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.8153750896453857s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.124641418457031e-05s
Availability | VoID file availability check for Openflights Routes took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.25687289237976074s
Reputation | Calculation of the PageRank for Openflights Routes took 0.020682096481323242s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.0279159545898438e-05s
Believability | Calculation of trust value for Openflights Routes took 7.152557373046875e-06s
INFO | --- Analysis for kasabi-openflights-routes took 2.8603506088256836s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.267692565917969e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2893795967102051s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020879745483398438s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.961822509765625e-05s
Believability | Calculation of trust value for Klappstuhlclub took 6.9141387939453125e-06s
INFO | --- Analysis for klappstuhlclub took 2.821706771850586s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.26358652114868164s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.079673767089844e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 6.198883056640625e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 2.866738796234131s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.124641418457031e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.27307701110839844s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020792484283447266s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.075599670410156e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.198883056640625e-06s
INFO | --- Analysis for knowledge-map took 2.8041486740112305s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.076957702636719e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2481234073638916s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 7.104873657226562e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 5.9604644775390625e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 2.8910443782806396s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.0531158447265625e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.25292444229125977s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 7.867813110351562e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.785869836807251s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.1484832763671875e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.25657129287719727s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.170967102050781e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 6.9141387939453125e-06s
INFO | --- Analysis for ktr took 2.8689370155334473s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 4.3392181396484375e-05s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2716481685638428s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.021047115325927734s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 4.267692565917969e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 6.9141387939453125e-06s
INFO | --- Analysis for kupkb took 2.859260082244873s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.315376281738281e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.26071643829345703s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.24249267578125e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 8.106231689453125e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.8469479084014893s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 4.4345855712890625e-05s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2640085220336914s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02082991600036621s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.43865966796875e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 8.106231689453125e-06s
INFO | --- Analysis for l3s-dblp took 2.875854969024658s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 4.6253204345703125e-05s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.2605006694793701s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007245540618896484s
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 6.9141387939453125e-06s
INFO | --- Analysis for lak-dataset took 2.795055627822876s
Availability | SPARQL endpoint availability check for LATC Linksets took 5.5789947509765625e-05s
Availability | VoID file availability check for LATC Linksets took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.2625582218170166s
Reputation | Calculation of the PageRank for LATC Linksets took 0.021313190460205078s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0009567737579345703s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.552436828613281e-05s
Believability | Calculation of trust value for LATC Linksets took 7.3909759521484375e-06s
INFO | --- Analysis for latc-linksets took 2.8205697536468506s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.1961669921875e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.27271056175231934s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 6.9141387939453125e-06s
INFO | --- Analysis for lcc took 2.8674612045288086s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.38690185546875e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2694857120513916s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011849403381347656s
Believability | Calculation of trust value for Library of Congress Subject Headings took 7.152557373046875e-06s
INFO | --- Analysis for lcsh took 3.480055809020996s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.363059997558594e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2535073757171631s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.273124694824219e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 6.67572021484375e-06s
INFO | --- Analysis for lcsubjects took 3.338083505630493s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.1961669921875e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.26347804069519043s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.02328348159790039s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0011136531829833984s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.8623809814453125e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 7.152557373046875e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.8464932441711426s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.482269287109375e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.00040793418884277344s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.27115559577941895s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.02077317237854004s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0008480548858642578s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.361701965332031e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 7.3909759521484375e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.8447048664093018s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.1961669921875e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.2533299922943115s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.9802322387695312e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 7.867813110351562e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.7502529621124268s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.172325134277344e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.2655937671661377s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.552436828613281e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 7.3909759521484375e-06s
INFO | --- Analysis for legislation-openuplabs took 2.8521652221679688s
Availability | SPARQL endpoint availability check for lemonUby took 4.1961669921875e-05s
Availability | VoID file availability check for lemonUby took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for lemonUby took 0.26439523696899414s
Reputation | Calculation of the PageRank for lemonUby took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.246566772460938e-05s
Believability | Calculation of trust value for lemonUby took 7.62939453125e-06s
INFO | --- Analysis for lemonuby took 2.8323142528533936s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.2438507080078125e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.2368478775024414s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.457069396972656e-05s
Believability | Calculation of trust value for LemonWiktionary took 7.152557373046875e-06s
INFO | --- Analysis for lemonwiktionary took 2.878277540206909s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 4.172325134277344e-05s
Availability | VoID file availability check for LEXIN-RDF took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.24998712539672852s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for LEXIN-RDF took 6.9141387939453125e-06s
INFO | --- Analysis for lexin-rdf took 2.8774523735046387s
Availability | SPARQL endpoint availability check for lexinfo took 5.984306335449219e-05s
Availability | VoID file availability check for lexinfo took 0.0003132820129394531s
Completeness | Calculation of interlinking completeness for lexinfo took 0.27870965003967285s
Reputation | Calculation of the PageRank for lexinfo took 0.021353721618652344s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0010175704956054688s
Interlinking | Calculation of Clustering coefficient for lexinfo took 0.00010061264038085938s
Believability | Calculation of trust value for lexinfo took 7.867813110351562e-06s
INFO | --- Analysis for lexinfo took 2.845759868621826s
Availability | SPARQL endpoint availability check for Lexvo took 4.2438507080078125e-05s
Availability | VoID file availability check for Lexvo took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2630600929260254s
Reputation | Calculation of the PageRank for Lexvo took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00016999244689941406s
Believability | Calculation of trust value for Lexvo took 7.3909759521484375e-06s
INFO | --- Analysis for lexvo took 2.831066131591797s
Availability | SPARQL endpoint availability check for LIBRIS took 0.26169729232788086s
Availability | VoID file availability check for LIBRIS took 0.0005040168762207031s
Extra | Recovery of all triples for LIBRIS took 6.2902748584747314s
Performance | Total latancy measurement for LIBRIS took 0.7077057361602783s
Amount of data | Number of triples check for LIBRIS took 25.165969848632812s
Interoperability | New terms check for LIBRIS took 15.23523211479187s
Versatility | Languages check for LIBRIS took 0.1563711166381836s
Interpretability | Number of blank nodes check for LIBRIS took 300.0934188365936s
Security | Check HTTPS for LIBRIS took 0.368680477142334s
Interpretability | RDF structures check for LIBRIS took 0.27313995361328125s
Versatility | Serialization formats check for LIBRIS took 0.18762421607971191s
Availability | RDF dump link check for LIBRIS took 0.1467747688293457s
License | MR license check for LIBRIS took 0.21857857704162598s
License | HR license check for LIBRIS took 0.20239019393920898s
Amount of data | Number of property check for LIBRIS took 0.1572883129119873s
Understandability | Number of label check for LIBRIS took 0.28610706329345703s
Understandability | URI regex check for LIBRIS took 0.33548736572265625s
Understandability | Vocabs check for LIBRIS took 0.1458892822265625s
Verifiability | Authors check for LIBRIS took 0.19103050231933594s
Verifiability | Publishers check for LIBRIS took 0.1523442268371582s
Performance | Throughput check for LIBRIS took 11.198543787002563s
Amount of data | Check the number of entities for LIBRIS took 3.409385681152344e-05s
Verifiability | Contribs. check for LIBRIS took 0.16067266464233398s
Interlinking | sameAs chians check for LIBRIS took 0.266019344329834s
Interlinking | skos check for LIBRIS took 0.2614269256591797s
Interlinking | skos check for LIBRIS took 0.1383366584777832s
Timeliness | dataset update frequency check for LIBRIS took 0.13894128799438477s
Currency | Creation date check for LIBRIS took 0.34702301025390625s
Currency | Modification date check for LIBRIS took 0.5987794399261475s
Rep.Conc. | URIs length for LIBRIS took 79.80401253700256s
Interoperability | New vocabularies check for LIBRIS took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.16296958923339844s
Accuracy | Check Functional Property for LIBRIS took 0.17025470733642578s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.17109131813049316s
Accuracy | Check Datatype consistency for LIBRIS took 0.26128244400024414s
Consistency | Disjoint class check for LIBRIS took 0.16239190101623535s
Consistency | Check Misplaced properties for LIBRIS took 62.05453419685364s
Consistency | Misplaced classes for LIBRIS took 1.1130218505859375s
Consistency | Check Ontology hijacking for LIBRIS took 3.214233875274658s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3174288272857666s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 63.051682472229004s
Conciseness | Check Extensional conciseness for LIBRIS took 0.27768754959106445s
Conciseness | Check Intensional conciseness for LIBRIS took 0.4246253967285156s
Security | Sign check for LIBRIS took 0.1840832233428955s
Availability | Check URIs Dereferenciability for LIBRIS took 14.044556379318237s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.8235821723937988s
Reputation | Calculation of the PageRank for LIBRIS took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006771087646484375s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00010251998901367188s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.9073486328125e-06s
Believability | Calculation of trust value for LIBRIS took 8.106231689453125e-06s
INFO | --- Analysis for libris took 1080.9891533851624s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.13901233673095703s
Availability | VoID file availability check for Public Library of Veroia took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.7154521942138672s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.462501525878906e-05s
Believability | Calculation of trust value for Public Library of Veroia took 7.867813110351562e-06s
INFO | --- Analysis for libver took 3.9003360271453857s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 4.315376281738281e-05s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.26255226135253906s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 7.963180541992188e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 7.62939453125e-06s
INFO | --- Analysis for lichfield-spending took 2.833364248275757s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.315376281738281e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.24411249160766602s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 4.124641418457031e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 6.67572021484375e-06s
INFO | --- Analysis for lime took 2.81674861907959s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.267692565917969e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.3022620677947998s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00011110305786132812s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 5.9604644775390625e-06s
INFO | --- Analysis for lingvoj took 2.900988817214966s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.363059997558594e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.00038933753967285156s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.23771381378173828s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.02094268798828125s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Crunchbase took 8.344650268554688e-06s
INFO | --- Analysis for linked-crunchbase took 2.86795973777771s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 4.220008850097656e-05s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2876901626586914s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.033348083496094e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.9141387939453125e-06s
INFO | --- Analysis for linked-drugs took 2.788388967514038s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.315376281738281e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.2297680377960205s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.679794311523438e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 6.4373016357421875e-06s
INFO | --- Analysis for linked-edgar took 2.7976503372192383s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.2815556526184082s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.512901306152344e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.152557373046875e-06s
INFO | --- Analysis for linked-eurostat took 2.860142469406128s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.124641418457031e-05s
Availability | VoID file availability check for linked hypernyms took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2589750289916992s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0008261203765869141s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.200241088867188e-05s
Believability | Calculation of trust value for linked hypernyms took 7.867813110351562e-06s
INFO | --- Analysis for linked-hypernyms took 2.8937876224517822s
Availability | SPARQL endpoint availability check for Linked Life Data took 4.1961669921875e-05s
Availability | VoID file availability check for Linked Life Data took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.26897335052490234s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.00543212890625e-05s
Believability | Calculation of trust value for Linked Life Data took 1.1920928955078125e-05s
INFO | --- Analysis for linked-life-data took 2.858424663543701s
Availability | SPARQL endpoint availability check for Linked Logainm took 4.076957702636719e-05s
Availability | VoID file availability check for Linked Logainm took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.26073575019836426s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.462501525878906e-05s
Believability | Calculation of trust value for Linked Logainm took 7.3909759521484375e-06s
INFO | --- Analysis for linked-logainm took 2.7745306491851807s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.267692565917969e-05s
Availability | VoID file availability check for Linked NUTS took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.2540628910064697s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020959138870239258s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.3882598876953125e-05s
Believability | Calculation of trust value for Linked NUTS took 1.3113021850585938e-05s
INFO | --- Analysis for linked-nuts took 2.8106424808502197s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 5.936622619628906e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.00033020973205566406s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.2519493103027344s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020720243453979492s
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.0007047653198242188s
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.106231689453125e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 2.901212215423584s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.2755584716796875s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 1.2159347534179688e-05s
INFO | --- Analysis for linked-open-camera took 2.783217430114746s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Open Commerce took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.26682043075561523s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0279159545898438e-05s
Believability | Calculation of trust value for Linked Open Commerce took 8.821487426757812e-06s
INFO | --- Analysis for linked-open-commerce took 2.8716301918029785s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 4.6253204345703125e-05s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.2530810832977295s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010156631469726562s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.2874603271484375e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 2.8308346271514893s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.00031638145446777344s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2385091781616211s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.322166442871094e-05s
Believability | Calculation of trust value for Linked Open Numbers took 9.298324584960938e-06s
INFO | --- Analysis for linked-open-numbers took 2.8176496028900146s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2535116672515869s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Open Piracy took 1.1920928955078125e-05s
INFO | --- Analysis for linked-open-piracy took 2.8678691387176514s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 6.985664367675781e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.2667868137359619s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.020554780960083008s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.147125244140625e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 9.059906005859375e-06s
INFO | --- Analysis for linked-open-senate took 2.8481199741363525s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 5.698204040527344e-05s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.2787435054779053s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020902633666992188s
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.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.7206878662109375e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.2159347534179688e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 2.8373522758483887s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.553794860839844e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.27140212059020996s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.5762786865234375e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 1.1920928955078125e-05s
INFO | --- Analysis for linked-periodicals took 2.818765878677368s
Availability | SPARQL endpoint availability check for Linked Index took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked Index took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2492663860321045s
Reputation | Calculation of the PageRank for Linked Index took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Index took 7.152557373046875e-06s
INFO | --- Analysis for linked-stockindex took 2.8625590801239014s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.25135350227355957s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007050037384033203s
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 7.3909759521484375e-06s
INFO | --- Analysis for linked-structured-product-labels took 2.8758902549743652s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.00038504600524902344s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2507948875427246s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.361701965332031e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 7.62939453125e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 2.8181822299957275s
Availability | SPARQL endpoint availability check for Linked TCGA took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked TCGA took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.28848719596862793s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.535385131835938e-05s
Believability | Calculation of trust value for Linked TCGA took 7.867813110351562e-06s
INFO | --- Analysis for linked-tcga took 2.851388931274414s
Availability | SPARQL endpoint availability check for Linked User Feedback took 5.888938903808594e-05s
Availability | VoID file availability check for Linked User Feedback took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.25195908546447754s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.886222839355469e-05s
Believability | Calculation of trust value for Linked User Feedback took 7.152557373046875e-06s
INFO | --- Analysis for linked-user-feedback took 2.8606619834899902s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.2438507080078125e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.27861809730529785s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.02100515365600586s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.581710815429688e-05s
Believability | Calculation of trust value for USPTO Patent data took 8.58306884765625e-06s
INFO | --- Analysis for linked-uspto-patent-data took 2.927804470062256s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2612619400024414s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 1.33514404296875e-05s
INFO | --- Analysis for linked-web-apis took 2.8699121475219727s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.1484832763671875e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.24823522567749023s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.170967102050781e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 1.2636184692382812e-05s
INFO | --- Analysis for linkedarc took 2.830143451690674s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.24706745147705078s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.021010637283325195s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.504753112792969e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 8.106231689453125e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.822033166885376s
Availability | SPARQL endpoint availability check for LinkedCT took 4.220008850097656e-05s
Availability | VoID file availability check for LinkedCT took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.2435295581817627s
Reputation | Calculation of the PageRank for LinkedCT took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.894371032714844e-05s
Believability | Calculation of trust value for LinkedCT took 7.62939453125e-06s
INFO | --- Analysis for linkedct took 2.6954476833343506s
Availability | SPARQL endpoint availability check for LinkedGeoData took 4.363059997558594e-05s
Availability | VoID file availability check for LinkedGeoData took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.25737833976745605s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00011730194091796875s
Believability | Calculation of trust value for LinkedGeoData took 1.2159347534179688e-05s
INFO | --- Analysis for linkedgeodata took 2.7723464965820312s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 0.0006177425384521484s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.28121280670166016s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.170967102050781e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 8.821487426757812e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 2.895487070083618s
Availability | SPARQL endpoint availability check for LinkedLCCN took 9.775689363479614s
Availability | VoID file availability check for LinkedLCCN took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.275179386138916s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010704994201660156s
Believability | Calculation of trust value for LinkedLCCN took 7.62939453125e-06s
INFO | --- Analysis for linkedlccn took 12.6102454662323s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.291534423828125e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2397933006286621s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020750045776367188s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.504753112792969e-05s
Believability | Calculation of trust value for LinkedMarkMail took 7.62939453125e-06s
INFO | --- Analysis for linkedmarkmail took 2.799171209335327s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 1.1610875129699707s
Availability | VoID file availability check for Linked Movie DataBase took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.272289514541626s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02113628387451172s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013756752014160156s
Believability | Calculation of trust value for Linked Movie DataBase took 7.152557373046875e-06s
INFO | --- Analysis for linkedmdb took 4.362622022628784s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 4.291534423828125e-05s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.25778889656066895s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.020834922790527344s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.43865966796875e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for linkedspending took 2.9011645317077637s
Availability | SPARQL endpoint availability check for LinkedStats took 4.124641418457031e-05s
Availability | VoID file availability check for LinkedStats took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.28018736839294434s
Reputation | Calculation of the PageRank for LinkedStats took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 2.9325485229492188e-05s
Believability | Calculation of trust value for LinkedStats took 1.2159347534179688e-05s
INFO | --- Analysis for linkedstats took 2.9154529571533203s
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.0003230571746826172s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.2856292724609375s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.000713348388671875s
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 6.9141387939453125e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.7989354133605957s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.1961669921875e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.2590022087097168s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020745277404785156s
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.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.147125244140625e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 6.9141387939453125e-06s
INFO | --- Analysis for linking-open-drug-data took 2.9004297256469727s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 4.172325134277344e-05s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.24955081939697266s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010752677917480469s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.3113021850585938e-05s
INFO | --- Analysis for linklion took 2.8960540294647217s
Availability | SPARQL endpoint availability check for Lion's Den took 4.267692565917969e-05s
Availability | VoID file availability check for Lion's Den took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.26066040992736816s
Reputation | Calculation of the PageRank for Lion's Den took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 2.9087066650390625e-05s
Believability | Calculation of trust value for Lion's Den took 7.62939453125e-06s
INFO | --- Analysis for lionsden took 2.8549554347991943s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 25.783676624298096s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.29006481170654297s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 4.76837158203125e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 9.298324584960938e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 29.44591975212097s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.2438507080078125e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.27448081970214844s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 7.62939453125e-06s
INFO | --- Analysis for livtdm took 2.827291965484619s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.38690185546875e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.24718928337097168s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.020765304565429688s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.9802322387695312e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 8.344650268554688e-06s
INFO | --- Analysis for livtdm2017 took 2.8427860736846924s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.26459598541259766s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 2.8371810913085938e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 7.3909759521484375e-06s
INFO | --- Analysis for lobi took 2.921359062194824s
Availability | SPARQL endpoint availability check for lobid-organisations took 4.267692565917969e-05s
Availability | VoID file availability check for lobid-organisations took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.24657344818115234s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.226799011230469e-05s
Believability | Calculation of trust value for lobid-organisations took 8.58306884765625e-06s
INFO | --- Analysis for lobid-organisations took 2.745112895965576s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 4.267692565917969e-05s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.2592895030975342s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010251998901367188s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 8.106231689453125e-06s
INFO | --- Analysis for lobid-resources took 2.8429243564605713s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.7206878662109375e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.24014663696289062s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020198822021484375s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 6.818771362304688e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.239776611328125e-05s
INFO | --- Analysis for loc took 2.8293676376342773s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 7.224082946777344e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.27973484992980957s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 2.8371810913085938e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 7.3909759521484375e-06s
INFO | --- Analysis for locv took 2.901160717010498s
Availability | SPARQL endpoint availability check for LOD-a-lot took 4.38690185546875e-05s
Availability | VoID file availability check for LOD-a-lot took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2520561218261719s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020310401916503906s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.6941299438476562e-05s
Believability | Calculation of trust value for LOD-a-lot took 7.152557373046875e-06s
INFO | --- Analysis for lod-a-lot took 2.783663034439087s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.2438507080078125e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.27842068672180176s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 2.765655517578125e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 6.9141387939453125e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.838944435119629s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.1961669921875e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0003209114074707031s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.26126575469970703s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 2.8133392333984375e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 7.62939453125e-06s
INFO | --- Analysis for lod-taiwan took 2.9022011756896973s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.1961669921875e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2749171257019043s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.463859558105469e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 8.106231689453125e-06s
INFO | --- Analysis for lod2-project-wiki took 2.921405553817749s
Availability | SPARQL endpoint availability check for LODAC BDLS took 4.38690185546875e-05s
Availability | VoID file availability check for LODAC BDLS took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2532069683074951s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.2479248046875e-05s
Believability | Calculation of trust value for LODAC BDLS took 8.106231689453125e-06s
INFO | --- Analysis for lodac-bdls took 2.868438720703125s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.1961669921875e-05s
Availability | VoID file availability check for LODRussia Math took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.27673912048339844s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.9325485229492188e-05s
Believability | Calculation of trust value for LODRussia Math took 7.62939453125e-06s
INFO | --- Analysis for lodrussia-math took 2.818312406539917s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.76837158203125e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.2646517753601074s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 2.8133392333984375e-05s
Believability | Calculation of trust value for LODRussia Nano took 7.62939453125e-06s
INFO | --- Analysis for lodrussia-nano took 2.867504596710205s
Availability | SPARQL endpoint availability check for LODStats took 4.9591064453125e-05s
Availability | VoID file availability check for LODStats took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for LODStats took 0.2724785804748535s
Reputation | Calculation of the PageRank for LODStats took 0.020519733428955078s
Interlinking | Calculation of Degree of Connection for LODStats took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LODStats took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for LODStats took 2.8371810913085938e-05s
Believability | Calculation of trust value for LODStats took 6.9141387939453125e-06s
INFO | --- Analysis for lodstats took 2.807579278945923s
Availability | SPARQL endpoint availability check for LODUM took 4.4345855712890625e-05s
Availability | VoID file availability check for LODUM took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for LODUM took 0.2673220634460449s
Reputation | Calculation of the PageRank for LODUM took 0.020815372467041016s
Interlinking | Calculation of Degree of Connection for LODUM took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.170967102050781e-05s
Believability | Calculation of trust value for LODUM took 8.106231689453125e-06s
INFO | --- Analysis for lodum took 2.8227248191833496s
Availability | SPARQL endpoint availability check for lofd took 4.291534423828125e-05s
Availability | VoID file availability check for lofd took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for lofd took 0.24906015396118164s
Reputation | Calculation of the PageRank for lofd took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for lofd took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for lofd took 3.075599670410156e-05s
Believability | Calculation of trust value for lofd took 1.2874603271484375e-05s
INFO | --- Analysis for lofd took 2.778599500656128s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 4.410743713378906e-05s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2642018795013428s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 4.792213439941406e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 8.344650268554688e-06s
INFO | --- Analysis for loius took 2.8157453536987305s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.315376281738281e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.2626643180847168s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.52587890625e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0010194778442382812s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 4.0531158447265625e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 8.106231689453125e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 2.8895304203033447s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 4.291534423828125e-05s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.26952624320983887s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.02113628387451172s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.001064300537109375s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 6.961822509765625e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 9.775161743164062e-06s
INFO | --- Analysis for london-gazette took 2.9260475635528564s
Availability | SPARQL endpoint availability check for Weather Stations took 4.267692565917969e-05s
Availability | VoID file availability check for Weather Stations took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.2647223472595215s
Reputation | Calculation of the PageRank for Weather Stations took 0.02192974090576172s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.821487426757812e-05s
Believability | Calculation of trust value for Weather Stations took 8.106231689453125e-06s
INFO | --- Analysis for los_metar took 2.8716933727264404s
Availability | SPARQL endpoint availability check for Lotico took 4.363059997558594e-05s
Availability | VoID file availability check for Lotico took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Lotico took 0.24343442916870117s
Reputation | Calculation of the PageRank for Lotico took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for Lotico took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.058547973632812e-05s
Believability | Calculation of trust value for Lotico took 8.344650268554688e-06s
INFO | --- Analysis for lotico took 2.837100028991699s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 4.4345855712890625e-05s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.27402782440185547s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02094268798828125s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 2.956390380859375e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 9.059906005859375e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 2.8282806873321533s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.3392181396484375e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.2525022029876709s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.021543025970458984s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.337860107421875e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 8.344650268554688e-06s
INFO | --- Analysis for lremap-auth took 2.7958011627197266s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 5.626678466796875e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2590334415435791s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.147125244140625e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 8.344650268554688e-06s
INFO | --- Analysis for lremap-conf took 2.7750320434570312s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.220008850097656e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.2739536762237549s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.0279159545898438e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.2874603271484375e-05s
INFO | --- Analysis for lremap-ri took 2.781616687774658s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.315376281738281e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.26687097549438477s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.123283386230469e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.33514404296875e-05s
INFO | --- Analysis for lremap-sub took 2.7628369331359863s
Availability | SPARQL endpoint availability check for LSQ took 4.6253204345703125e-05s
Availability | VoID file availability check for LSQ took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for LSQ took 0.2473587989807129s
Reputation | Calculation of the PageRank for LSQ took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.9325485229492188e-05s
Believability | Calculation of trust value for LSQ took 7.62939453125e-06s
INFO | --- Analysis for lsq took 2.7676658630371094s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.267692565917969e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.2681910991668701s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.0208892822265625s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.218650817871094e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 8.106231689453125e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.791245222091675s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.1484832763671875e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.265519380569458s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020270109176635742s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.337860107421875e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 7.152557373046875e-06s
INFO | --- Analysis for manchester-university-reading-lists took 2.7471160888671875s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.267692565917969e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.24076342582702637s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.8133392333984375e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 7.62939453125e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.811121940612793s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.410743713378906e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.2600691318511963s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020819902420043945s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 2.956390380859375e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 7.62939453125e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.848860263824463s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.267692565917969e-05s
Availability | VoID file availability check for MARC Codes List took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.25621533393859863s
Reputation | Calculation of the PageRank for MARC Codes List took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012421607971191406s
Believability | Calculation of trust value for MARC Codes List took 9.5367431640625e-06s
INFO | --- Analysis for marc-codes took 2.8901748657226562s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.291534423828125e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.27926111221313477s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02194499969482422s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.814697265625e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 8.344650268554688e-06s
INFO | --- Analysis for masc took 2.9315690994262695s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 5.91278076171875e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2628207206726074s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.647804260253906e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 7.62939453125e-06s
INFO | --- Analysis for masc-bn-nif took 2.8095805644989014s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.2863364219665527s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2593982219696045s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.02077198028564453s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0009365081787109375s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.3855438232421875e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 7.62939453125e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.092455148696899s
Availability | SPARQL endpoint availability check for medline took 5.221366882324219e-05s
Availability | VoID file availability check for medline took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for medline took 0.26625871658325195s
Reputation | Calculation of the PageRank for medline took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for medline took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for medline took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for medline took 3.24249267578125e-05s
Believability | Calculation of trust value for medline took 7.867813110351562e-06s
INFO | --- Analysis for medline took 2.874063014984131s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 4.267692565917969e-05s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.2659926414489746s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.723403930664062e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 7.867813110351562e-06s
INFO | --- Analysis for meducator took 2.9323983192443848s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.458427429199219e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2504425048828125s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020877599716186523s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 3.266334533691406e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 8.344650268554688e-06s
INFO | --- Analysis for mesh-finnish took 2.820737600326538s
Availability | SPARQL endpoint availability check for MeSH headings took 4.267692565917969e-05s
Availability | VoID file availability check for MeSH headings took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.27782106399536133s
Reputation | Calculation of the PageRank for MeSH headings took 0.02036738395690918s
Interlinking | Calculation of Degree of Connection for MeSH headings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.8848648071289062e-05s
Believability | Calculation of trust value for MeSH headings took 7.152557373046875e-06s
INFO | --- Analysis for mesh_headings took 2.846604824066162s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.744529724121094e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.24648571014404297s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.00104522705078125s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.4809112548828125e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 6.9141387939453125e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.8656256198883057s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.220008850097656e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.25956034660339355s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 3.0279159545898438e-05s
Believability | Calculation of trust value for MeSH pairs took 7.867813110351562e-06s
INFO | --- Analysis for mesh_pairs took 2.8191025257110596s
Availability | SPARQL endpoint availability check for MeSH titles took 4.1961669921875e-05s
Availability | VoID file availability check for MeSH titles took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.27498912811279297s
Reputation | Calculation of the PageRank for MeSH titles took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.0279159545898438e-05s
Believability | Calculation of trust value for MeSH titles took 7.3909759521484375e-06s
INFO | --- Analysis for mesh_titles took 2.8168742656707764s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.315376281738281e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2566356658935547s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 2.8371810913085938e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 7.62939453125e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.8595848083496094s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 5.340576171875e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.2567934989929199s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.02039027214050293s
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.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 2.956390380859375e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 7.867813110351562e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.8060076236724854s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.291534423828125e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.25528860092163086s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.021188020706176758s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.724761962890625e-05s
Believability | Calculation of trust value for MetaShare metadata model took 7.152557373046875e-06s
INFO | --- Analysis for metashare took 2.8179335594177246s
Availability | SPARQL endpoint availability check for MExiCo took 9.822845458984375e-05s
Availability | VoID file availability check for MExiCo took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for MExiCo took 0.27845025062561035s
Reputation | Calculation of the PageRank for MExiCo took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for MExiCo took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MExiCo took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.4345855712890625e-05s
Believability | Calculation of trust value for MExiCo took 6.67572021484375e-06s
INFO | --- Analysis for mexico took 2.983463764190674s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.2515864372253418s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02085733413696289s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.799003601074219e-05s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 2.8954288959503174s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.506111145019531e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.259265661239624s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010371208190917969s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for mismuseos-gnoss took 2.8875513076782227s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.1484832763671875e-05s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.26371240615844727s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 3.981590270996094e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.3909759521484375e-06s
INFO | --- Analysis for mlsa took 2.8840689659118652s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.1484832763671875e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.24898672103881836s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.8371810913085938e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 7.867813110351562e-06s
INFO | --- Analysis for mond took 2.8429126739501953s
Availability | SPARQL endpoint availability check for MONDIS took 4.2438507080078125e-05s
Availability | VoID file availability check for MONDIS took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for MONDIS took 0.2784905433654785s
Reputation | Calculation of the PageRank for MONDIS took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for MONDIS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MONDIS took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.8371810913085938e-05s
Believability | Calculation of trust value for MONDIS took 7.62939453125e-06s
INFO | --- Analysis for mondis took 2.8598101139068604s
Availability | SPARQL endpoint availability check for Monumentos took 4.220008850097656e-05s
Availability | VoID file availability check for Monumentos took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Monumentos took 0.24361157417297363s
Reputation | Calculation of the PageRank for Monumentos took 0.020232677459716797s
Interlinking | Calculation of Degree of Connection for Monumentos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Monumentos took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Monumentos took 2.7894973754882812e-05s
Believability | Calculation of trust value for Monumentos took 1.1920928955078125e-05s
INFO | --- Analysis for monumentos-zaragoza took 2.8313934803009033s
Availability | SPARQL endpoint availability check for MORElab took 4.1961669921875e-05s
Availability | VoID file availability check for MORElab took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for MORElab took 0.2509431838989258s
Reputation | Calculation of the PageRank for MORElab took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for MORElab took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MORElab took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.463859558105469e-05s
Believability | Calculation of trust value for MORElab took 6.4373016357421875e-06s
INFO | --- Analysis for morelab took 2.8477632999420166s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 4.2438507080078125e-05s
Availability | VoID file availability check for Mathematics Subject Classification took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.26389241218566895s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.654594421386719e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.2159347534179688e-05s
INFO | --- Analysis for msc took 2.8042097091674805s
Availability | SPARQL endpoint availability check for Multext-East took 4.220008850097656e-05s
Availability | VoID file availability check for Multext-East took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Multext-East took 0.26318979263305664s
Reputation | Calculation of the PageRank for Multext-East took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for Multext-East took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Multext-East took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.2901763916015625e-05s
Believability | Calculation of trust value for Multext-East took 1.1920928955078125e-05s
INFO | --- Analysis for multext-east took 2.8753435611724854s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 7.653236389160156e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.2653999328613281s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.1948089599609375e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 6.9141387939453125e-06s
INFO | --- Analysis for multilingualeulaw took 2.894636392593384s
Availability | SPARQL endpoint availability check for Multimedia Lab took 5.2928924560546875e-05s
Availability | VoID file availability check for Multimedia Lab took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2637820243835449s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.147125244140625e-05s
Believability | Calculation of trust value for Multimedia Lab took 7.3909759521484375e-06s
INFO | --- Analysis for multimedia-lab took 2.8146920204162598s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.1961669921875e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.2518446445465088s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 2.9087066650390625e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 1.0967254638671875e-05s
INFO | --- Analysis for munich-offener-haushalt took 2.825648784637451s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.6627509593963623s
Availability | VoID file availability check for Muninn World War I took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2692282199859619s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020905256271362305s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 9.369850158691406e-05s
Believability | Calculation of trust value for Muninn World War I took 7.62939453125e-06s
INFO | --- Analysis for muninn-world-war-i took 6.277811765670776s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.8160552978515625e-05s
Availability | VoID file availability check for Musei Italiani took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.2669351100921631s
Reputation | Calculation of the PageRank for Musei Italiani took 0.021691083908081055s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0009410381317138672s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 3.6716461181640625e-05s
Believability | Calculation of trust value for Musei Italiani took 7.867813110351562e-06s
INFO | --- Analysis for musei-italiani took 2.9029791355133057s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.458427429199219e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.27513813972473145s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020890474319458008s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010275840759277344s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for museosespania-gnoss took 2.862217664718628s
Availability | SPARQL endpoint availability check for Italian Museums took 1.6416442394256592s
Availability | VoID file availability check for Italian Museums took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.2563025951385498s
Reputation | Calculation of the PageRank for Italian Museums took 0.025435686111450195s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 0.00011038780212402344s
Believability | Calculation of trust value for Italian Museums took 7.867813110351562e-06s
INFO | --- Analysis for museums-in-italy took 4.510780334472656s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.458427429199219e-05s
Availability | VoID file availability check for MusicBrainz took 0.00033164024353027344s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.2606208324432373s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020448923110961914s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.0994415283203125e-05s
Believability | Calculation of trust value for MusicBrainz took 1.6450881958007812e-05s
INFO | --- Analysis for musicbrainz_ took 2.8232879638671875s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.2438507080078125e-05s
Availability | VoID file availability check for MusicNet Codex took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.2573843002319336s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.8371810913085938e-05s
Believability | Calculation of trust value for MusicNet Codex took 7.3909759521484375e-06s
INFO | --- Analysis for musicnet_codex took 2.8940093517303467s
Availability | SPARQL endpoint availability check for myExperiment took 4.267692565917969e-05s
Availability | VoID file availability check for myExperiment took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for myExperiment took 0.27948617935180664s
Reputation | Calculation of the PageRank for myExperiment took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0009558200836181641s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00011205673217773438s
Believability | Calculation of trust value for myExperiment took 7.62939453125e-06s
INFO | --- Analysis for my-experiment took 2.8053643703460693s
Availability | SPARQL endpoint availability check for My Family Lineage took 4.315376281738281e-05s
Availability | VoID file availability check for My Family Lineage took 0.00030350685119628906s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.24082636833190918s
Reputation | Calculation of the PageRank for My Family Lineage took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.440017700195312e-05s
Believability | Calculation of trust value for My Family Lineage took 6.9141387939453125e-06s
INFO | --- Analysis for my-family-lineage took 2.8057258129119873s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 4.267692565917969e-05s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.2700953483581543s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020721912384033203s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.000720977783203125s
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 1.239776611328125e-05s
INFO | --- Analysis for n-lex-as-linked-data took 2.8709380626678467s
Availability | SPARQL endpoint availability check for NAICS 2007 took 4.1484832763671875e-05s
Availability | VoID file availability check for NAICS 2007 took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.2522256374359131s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.02059006690979004s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.504753112792969e-05s
Believability | Calculation of trust value for NAICS 2007 took 7.62939453125e-06s
INFO | --- Analysis for naics-2007 took 2.8387722969055176s
Availability | SPARQL endpoint availability check for NAICS 2012 took 4.2438507080078125e-05s
Availability | VoID file availability check for NAICS 2012 took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.2635180950164795s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.245208740234375e-05s
Believability | Calculation of trust value for NAICS 2012 took 7.62939453125e-06s
INFO | --- Analysis for naics-2012 took 2.77569317817688s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.26494336128234863s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0009984970092773438s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.555152893066406e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for nalt took 2.831749200820923s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 4.220008850097656e-05s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.2568974494934082s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02099609375s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 5.888938903808594e-05s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 7.62939453125e-06s
INFO | --- Analysis for national-diet-library-authorities took 2.8787972927093506s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 4.363059997558594e-05s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.26517343521118164s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 4.935264587402344e-05s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.2159347534179688e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 2.86783766746521s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.1242995262145996s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.26306629180908203s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.0531158447265625e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 6.67572021484375e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 4.7006776332855225s
Availability | SPARQL endpoint availability check for Naturopathy took 4.220008850097656e-05s
Availability | VoID file availability check for Naturopathy took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.2888979911804199s
Reputation | Calculation of the PageRank for Naturopathy took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 2.765655517578125e-05s
Believability | Calculation of trust value for Naturopathy took 1.239776611328125e-05s
INFO | --- Analysis for naturopathy2 took 2.879338502883911s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.25933837890625s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.266334533691406e-05s
Believability | Calculation of trust value for NCI Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for nci-thesaurus took 2.8353829383850098s
Availability | SPARQL endpoint availability check for NDF-RT took 4.172325134277344e-05s
Availability | VoID file availability check for NDF-RT took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.27576541900634766s
Reputation | Calculation of the PageRank for NDF-RT took 0.021662235260009766s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 2.86102294921875e-05s
Believability | Calculation of trust value for NDF-RT took 8.821487426757812e-06s
INFO | --- Analysis for ndf-rt took 2.791490316390991s
Availability | SPARQL endpoint availability check for Near took 4.2438507080078125e-05s
Availability | VoID file availability check for Near took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Near took 0.25360774993896484s
Reputation | Calculation of the PageRank for Near took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for Near took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Near took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Near took 9.059906005859375e-05s
Believability | Calculation of trust value for Near took 7.867813110351562e-06s
INFO | --- Analysis for near took 2.8297033309936523s
Availability | SPARQL endpoint availability check for Neel took 4.2438507080078125e-05s
Availability | VoID file availability check for Neel took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Neel took 0.26108622550964355s
Reputation | Calculation of the PageRank for Neel took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for Neel took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neel took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Neel took 2.9087066650390625e-05s
Believability | Calculation of trust value for Neel took 8.106231689453125e-06s
INFO | --- Analysis for neel took 2.8268496990203857s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 5.435943603515625e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.278670072555542s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 2.7418136596679688e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 1.2159347534179688e-05s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.9170656204223633s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.291534423828125e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2650575637817383s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020730972290039062s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.86102294921875e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for neurolex-wiki took 2.8488948345184326s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.24474716186523438s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020252227783203125s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 7.319450378417969e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 7.62939453125e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 2.7618916034698486s
Availability | SPARQL endpoint availability check for Newsweek took 4.1961669921875e-05s
Availability | VoID file availability check for Newsweek took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Newsweek took 0.2553272247314453s
Reputation | Calculation of the PageRank for Newsweek took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Newsweek took 2.765655517578125e-05s
Believability | Calculation of trust value for Newsweek took 7.867813110351562e-06s
INFO | --- Analysis for newsweek took 2.779430627822876s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.27178144454956055s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.000972747802734375s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00011491775512695312s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for nextweb-gnoss took 2.8993279933929443s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.172325134277344e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.26337504386901855s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.130073547363281e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 7.62939453125e-06s
INFO | --- Analysis for nhs-jargon took 2.7729332447052s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.3392181396484375e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.23555541038513184s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020661115646362305s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.552436828613281e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 8.344650268554688e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.758962392807007s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2696974277496338s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020536422729492188s
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.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.0040740966796875e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.152557373046875e-06s
INFO | --- Analysis for nlr-dataset-mod took 2.8781964778900146s
Availability | SPARQL endpoint availability check for Nobel Prizes took 4.649162292480469e-05s
Availability | VoID file availability check for Nobel Prizes took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.2577342987060547s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.131431579589844e-05s
Believability | Calculation of trust value for Nobel Prizes took 7.867813110351562e-06s
INFO | --- Analysis for nobelprizes took 2.845247507095337s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 4.220008850097656e-05s
Availability | VoID file availability check for Nomenclator Asturias took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.25481319427490234s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 7.772445678710938e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 7.62939453125e-06s
INFO | --- Analysis for nomenclator-asturias took 2.873373508453369s
Availability | SPARQL endpoint availability check for nomisma took 5.507469177246094e-05s
Availability | VoID file availability check for nomisma took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for nomisma took 0.2928929328918457s
Reputation | Calculation of the PageRank for nomisma took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for nomisma took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for nomisma took 2.9325485229492188e-05s
Believability | Calculation of trust value for nomisma took 7.152557373046875e-06s
INFO | --- Analysis for nomisma took 2.819354772567749s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 4.2438507080078125e-05s
Availability | VoID file availability check for Norwegian geo-divisions took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.2624068260192871s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.3392181396484375e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 7.867813110351562e-06s
INFO | --- Analysis for norwegian-geo-divisions took 2.8204615116119385s
Availability | SPARQL endpoint availability check for NorwegianSoE took 6.651878356933594e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.26053595542907715s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 2.9325485229492188e-05s
Believability | Calculation of trust value for NorwegianSoE took 7.867813110351562e-06s
INFO | --- Analysis for norwegiansoe took 2.846102237701416s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.172325134277344e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2759287357330322s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.647804260253906e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 7.62939453125e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.799764633178711s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.172325134277344e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0003170967102050781s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2506370544433594s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 2.8371810913085938e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 7.867813110351562e-06s
INFO | --- Analysis for npg took 2.8377416133880615s
Availability | SPARQL endpoint availability check for NPM took 4.1484832763671875e-05s
Availability | VoID file availability check for NPM took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for NPM took 0.25301098823547363s
Reputation | Calculation of the PageRank for NPM took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for NPM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NPM took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for NPM took 3.1948089599609375e-05s
Believability | Calculation of trust value for NPM took 7.3909759521484375e-06s
INFO | --- Analysis for npm took 2.882044553756714s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.011742115020751953s
Availability | VoID file availability check for NTNU special collections took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.2655758857727051s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.245208740234375e-05s
Believability | Calculation of trust value for NTNU special collections took 7.867813110351562e-06s
INFO | --- Analysis for ntnusc took 2.824735403060913s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 8.7738037109375e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2701563835144043s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.021118640899658203s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00010251998901367188s
Believability | Calculation of trust value for NUTS (GeoVocab) took 8.58306884765625e-06s
INFO | --- Analysis for nuts-geovocab took 2.865954875946045s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 4.124641418457031e-05s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.24676156044006348s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.534027099609375e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 7.3909759521484375e-06s
INFO | --- Analysis for nvd took 2.8130125999450684s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 4.315376281738281e-05s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0004055500030517578s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.2704293727874756s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.915496826171875e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 8.106231689453125e-06s
INFO | --- Analysis for nvs took 2.83760929107666s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 5.602836608886719e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.28046345710754395s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018453598022460938s
Believability | Calculation of trust value for New York Times - Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.8387739658355713s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.3392181396484375e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.2878446578979492s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.020735502243041992s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 0.0001201629638671875s
Believability | Calculation of trust value for American National Corpus - Open Portion took 6.9141387939453125e-06s
INFO | --- Analysis for o-anc took 2.94956111907959s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.482269287109375e-05s
Availability | VoID file availability check for OANetzwerk took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.27306604385375977s
Reputation | Calculation of the PageRank for OANetzwerk took 0.02092146873474121s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 2.8133392333984375e-05s
Believability | Calculation of trust value for OANetzwerk took 8.106231689453125e-06s
INFO | --- Analysis for oanetzwerk took 2.831911563873291s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.38690185546875e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.2525339126586914s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 2.765655517578125e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 8.106231689453125e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.797389507293701s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 4.100799560546875e-05s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.2575187683105469s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02077317237854004s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 9.274482727050781e-05s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 8.106231689453125e-06s
INFO | --- Analysis for ocd took 2.892664909362793s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.291534423828125e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2555503845214844s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.600120544433594e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-borehole took 2.9192304611206055s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 4.220008850097656e-05s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.27995800971984863s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.296966552734375e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.2636184692382812e-05s
INFO | --- Analysis for oceandrilling-codices took 2.790247917175293s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 4.744529724121094e-05s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.2641568183898926s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.123283386230469e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.3113021850585938e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 2.885148763656616s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 4.172325134277344e-05s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.24499773979187012s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.123283386230469e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.1682510375976562e-05s
INFO | --- Analysis for oceandrilling-forams took 2.889779806137085s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 7.033348083496094e-05s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.25922584533691406s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.021389484405517578s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0009181499481201172s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.695487976074219e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-janus took 2.841400623321533s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 5.2928924560546875e-05s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.2871849536895752s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020859718322753906s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.5762786865234375e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 7.62939453125e-06s
INFO | --- Analysis for oceandrilling-janusamp took 2.9789652824401855s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 4.458427429199219e-05s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2544286251068115s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-ldeo took 2.848205089569092s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 5.9604644775390625e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.28000831604003906s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.412101745605469e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 6.67572021484375e-06s
INFO | --- Analysis for oclc-fast took 2.867091178894043s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.1484832763671875e-05s
Availability | VoID file availability check for Open Data Communities took 0.00030803680419921875s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.26325464248657227s
Reputation | Calculation of the PageRank for Open Data Communities took 0.022091150283813477s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0009515285491943359s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.409385681152344e-05s
Believability | Calculation of trust value for Open Data Communities took 6.9141387939453125e-06s
INFO | --- Analysis for odc took 2.778029441833496s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.26297950744628906s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.8371810913085938e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 7.62939453125e-06s
INFO | --- Analysis for odc-imd-environment-score took 2.819159507751465s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 5.2928924560546875e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.25560927391052246s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 3.075599670410156e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 7.62939453125e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 2.833850860595703s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 4.267692565917969e-05s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.27399754524230957s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.337860107421875e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 7.867813110351562e-06s
INFO | --- Analysis for odc-lsoa took 2.8204188346862793s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.1484832763671875e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2556791305541992s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 7.62939453125e-06s
INFO | --- Analysis for odc-population-2005 took 2.820589780807495s
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.00025916099548339844s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.249619722366333s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0009274482727050781s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 3.457069396972656e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 7.867813110351562e-06s
INFO | --- Analysis for ods took 2.8206629753112793s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 4.2438507080078125e-05s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.26059556007385254s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.34600830078125e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for oecd-linked-data took 2.8435585498809814s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.220008850097656e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.2684485912322998s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 2.8848648071289062e-05s
Believability | Calculation of trust value for Offener Haushalt took 7.3909759521484375e-06s
INFO | --- Analysis for offener-haushalt took 2.8522768020629883s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 5.269050598144531e-05s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.24806475639343262s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 3.910064697265625e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.2159347534179688e-05s
INFO | --- Analysis for ogolod took 2.7887325286865234s
Availability | SPARQL endpoint availability check for OLiA took 4.673004150390625e-05s
Availability | VoID file availability check for OLiA took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for OLiA took 0.25037550926208496s
Reputation | Calculation of the PageRank for OLiA took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for OLiA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00011992454528808594s
Believability | Calculation of trust value for OLiA took 7.62939453125e-06s
INFO | --- Analysis for olia took 2.8388025760650635s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.1961669921875e-05s
Availability | VoID file availability check for OLiA Discourse took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.2693347930908203s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.743171691894531e-05s
Believability | Calculation of trust value for OLiA Discourse took 7.152557373046875e-06s
INFO | --- Analysis for olia-discourse took 2.750540256500244s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.2438507080078125e-05s
Availability | VoID file availability check for OmegaWiki took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.2543163299560547s
Reputation | Calculation of the PageRank for OmegaWiki took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 3.0040740966796875e-05s
Believability | Calculation of trust value for OmegaWiki took 7.152557373046875e-06s
INFO | --- Analysis for omegawiki took 2.866074323654175s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.172325134277344e-05s
Availability | VoID file availability check for OntoBeef Domain took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.27808451652526855s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020740747451782227s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.291534423828125e-05s
Believability | Calculation of trust value for OntoBeef Domain took 7.3909759521484375e-06s
INFO | --- Analysis for ontobeef-domain took 2.845226526260376s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.172325134277344e-05s
Availability | VoID file availability check for Ontos News Portal took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.27787065505981445s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 8.797645568847656e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.62939453125e-06s
INFO | --- Analysis for ontos-news-portal took 2.8968400955200195s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.220008850097656e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.26494503021240234s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.504753112792969e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 7.62939453125e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 2.917247772216797s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.220008850097656e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2601490020751953s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.8848648071289062e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.846967935562134s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.1961669921875e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.2487344741821289s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.3392181396484375e-05s
Believability | Calculation of trust value for Open Data Euskadi took 9.059906005859375e-06s
INFO | --- Analysis for open-data-euskadi took 2.767436981201172s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.172325134277344e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.23346185684204102s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010275840759277344s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.62939453125e-06s
INFO | --- Analysis for open-data-risp took 2.813934326171875s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for Open Data Thesaurus took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.24965143203735352s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.462501525878906e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for open-data-thesaurus took 2.8250484466552734s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 6.341934204101562e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.25896334648132324s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.02022266387939453s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 2.8133392333984375e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 7.867813110351562e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.857771396636963s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.124641418457031e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.24372148513793945s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020807504653930664s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.604194641113281e-05s
Believability | Calculation of trust value for Open Election Data Project took 9.298324584960938e-06s
INFO | --- Analysis for open-election-data-project took 2.8781261444091797s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.2576940059661865s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.440017700195312e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 7.62939453125e-06s
INFO | --- Analysis for open-energy-info-wiki took 2.929852247238159s
Availability | SPARQL endpoint availability check for Open Library took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Library took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Open Library took 0.2563161849975586s
Reputation | Calculation of the PageRank for Open Library took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for Open Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.961822509765625e-05s
Believability | Calculation of trust value for Open Library took 6.67572021484375e-06s
INFO | --- Analysis for open-library took 2.793933391571045s
Availability | SPARQL endpoint availability check for Open Directory took 4.172325134277344e-05s
Availability | VoID file availability check for Open Directory took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Open Directory took 0.2550222873687744s
Reputation | Calculation of the PageRank for Open Directory took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for Open Directory took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Directory took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Open Directory took 2.6702880859375e-05s
Believability | Calculation of trust value for Open Directory took 7.3909759521484375e-06s
INFO | --- Analysis for open_directory took 2.8341922760009766s
Availability | SPARQL endpoint availability check for flyatlas took 5.650520324707031e-05s
Availability | VoID file availability check for flyatlas took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for flyatlas took 0.26323914527893066s
Reputation | Calculation of the PageRank for flyatlas took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for flyatlas took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for flyatlas took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for flyatlas took 2.7894973754882812e-05s
Believability | Calculation of trust value for flyatlas took 7.152557373046875e-06s
INFO | --- Analysis for openbiomed-flyatlas took 2.824310779571533s
Availability | SPARQL endpoint availability check for OpenCalais took 4.220008850097656e-05s
Availability | VoID file availability check for OpenCalais took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2575359344482422s
Reputation | Calculation of the PageRank for OpenCalais took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for OpenCalais took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010752677917480469s
Believability | Calculation of trust value for OpenCalais took 8.106231689453125e-06s
INFO | --- Analysis for opencalais took 2.8176510334014893s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.1961669921875e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0003390312194824219s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.24986982345581055s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.200241088867188e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 7.867813110351562e-06s
INFO | --- Analysis for opencorporates took 2.7701592445373535s
Availability | SPARQL endpoint availability check for OpenCyc took 4.267692565917969e-05s
Availability | VoID file availability check for OpenCyc took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2800929546356201s
Reputation | Calculation of the PageRank for OpenCyc took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for OpenCyc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010609626770019531s
Believability | Calculation of trust value for OpenCyc took 7.62939453125e-06s
INFO | --- Analysis for opencyc took 2.8633229732513428s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.2378699779510498s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.314018249511719e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 2.7580690383911133s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.30684661865234375s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0008327960968017578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.7903101444244385s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.25905585289001465s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.8177311420440674s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.23925495147705078s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.780686140060425s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.24350690841674805s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.854605197906494s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.2549753189086914s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020518064498901367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.9099178314208984s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.24553561210632324s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.021188020706176758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0008068084716796875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.7944605350494385s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2655913829803467s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007567405700683594s
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 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.9330408573150635s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.256253719329834s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.021073579788208008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 2.935762405395508s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2712414264678955s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020797252655029297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 2.830106258392334s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.24991083145141602s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.872087240219116s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.7206878662109375e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.28786206245422363s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.9124746322631836s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0003466606140136719s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.2761421203613281s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.820117235183716s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.25535130500793457s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020739316940307617s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.8062920570373535s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.26152706146240234s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.8705532550811768s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2385549545288086s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0010602474212646484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 5.030632019042969e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.8238890171051025s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.26497912406921387s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.811981201171875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.8549439907073975s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2704472541809082s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.935264587402344e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.8912644386291504s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2641110420227051s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020460128784179688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.7784225940704346s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.27805209159851074s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.8542795181274414s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.029273986816406e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.25086498260498047s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.811293363571167s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.25290560722351074s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.814589738845825s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 6.818771362304688e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.26226234436035156s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020309925079345703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.854198694229126s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 5.936622619628906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.2515232563018799s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020467758178710938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.8106484413146973s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2606074810028076s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.02034735679626465s
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.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.884646415710449s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2515678405761719s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.9877238273620605s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.25902581214904785s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.4182913303375244s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.2634878158569336s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020236492156982422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.903099775314331s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.25589752197265625s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.824498414993286s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.00043511390686035156s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.2873876094818115s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.9487719535827637s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.24932122230529785s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.7642974853515625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.8429651260375977s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 8.678436279296875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2694740295410156s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.8667943477630615s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.25528883934020996s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.482269287109375e-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.8705859184265137s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.27476954460144043s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02070474624633789s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.8604140281677246s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.26032185554504395s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.021162033081054688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.8398025035858154s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.25532054901123047s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020718812942504883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.8648221492767334s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.26897478103637695s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020810842514038086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.839280843734741s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2537498474121094s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.8385202884674072s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.26351022720336914s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020527362823486328s
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.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.9180169105529785s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.25445985794067383s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.7637431621551514s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.2631521224975586s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 2.864187717437744s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2534463405609131s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020684480667114258s
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.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.830472707748413s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2503011226654053s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007431507110595703s
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 2.84559965133667s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.315376281738281e-05s
Availability | VoID file availability check for Open Data of Ecuador took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2737767696380615s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.630752563476562e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 7.867813110351562e-06s
INFO | --- Analysis for opendataec took 2.8252217769622803s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.27233362197875977s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 2.8033058643341064s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.7206878662109375e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.247206449508667s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.8351104259490967s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.315376281738281e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2440030574798584s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.8813676834106445s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.315376281738281e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2792477607727051s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.823906421661377s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0002193450927734375s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.26867127418518066s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.5762786865234375e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.849759101867676s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.315376281738281e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.24907875061035156s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.0203554630279541s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.8213295936584473s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.220008850097656e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2643272876739502s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02071356773376465s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.8103578090667725s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.27649712562561035s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020421743392944336s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.552436828613281e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.791869640350342s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.124641418457031e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.26243019104003906s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.760058879852295s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 4.9591064453125e-05s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2798130512237549s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 2.7179718017578125e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 7.62939453125e-06s
INFO | --- Analysis for openlink-lod-cache took 2.8598005771636963s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.1961669921875e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.2648594379425049s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.179115295410156e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 7.62939453125e-06s
INFO | --- Analysis for openlylocal took 2.8307883739471436s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 4.4345855712890625e-05s
Availability | VoID file availability check for OpenMobileNetwork took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.25011157989501953s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02118659019470215s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 8.463859558105469e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.33514404296875e-05s
INFO | --- Analysis for openmobilenetwork took 2.8131253719329834s
Availability | SPARQL endpoint availability check for OpenTox took 4.410743713378906e-05s
Availability | VoID file availability check for OpenTox took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for OpenTox took 0.24304771423339844s
Reputation | Calculation of the PageRank for OpenTox took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.0517578125e-05s
Believability | Calculation of trust value for OpenTox took 8.58306884765625e-06s
INFO | --- Analysis for opentox took 2.790506601333618s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.601478576660156e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.23950433731079102s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 8.106231689453125e-06s
INFO | --- Analysis for openuplabs took 2.8584654331207275s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 5.340576171875e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.2632772922515869s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 2.9802322387695312e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 8.344650268554688e-06s
INFO | --- Analysis for opus took 2.8513121604919434s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 4.291534423828125e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.2658224105834961s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.6716461181640625e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 1.2636184692382812e-05s
INFO | --- Analysis for orcid took 2.857128381729126s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 4.553794860839844e-05s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2575247287750244s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02038097381591797s
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.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.465217590332031e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 2.8738131523132324s
Availability | SPARQL endpoint availability check for oreilly took 4.458427429199219e-05s
Availability | VoID file availability check for oreilly took 0.00033164024353027344s
Completeness | Calculation of interlinking completeness for oreilly took 0.26241254806518555s
Reputation | Calculation of the PageRank for oreilly took 0.020868778228759766s
Interlinking | Calculation of Degree of Connection for oreilly took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.9591064453125e-05s
Believability | Calculation of trust value for oreilly took 1.2636184692382812e-05s
INFO | --- Analysis for oreilly took 2.879683494567871s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 4.1961669921875e-05s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.25852203369140625s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.604194641113281e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.4066696166992188e-05s
INFO | --- Analysis for organic-edunet took 2.8040871620178223s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.807941436767578s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.23762893676757812s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.177757263183594e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 7.867813110351562e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 8.15763258934021s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 4.076957702636719e-05s
Availability | VoID file availability check for OSM Semantic Network took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2610433101654053s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020493745803833008s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.886222839355469e-05s
Believability | Calculation of trust value for OSM Semantic Network took 5.9604644775390625e-06s
INFO | --- Analysis for osm-semantic-network took 2.776752233505249s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.23592042922973633s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 2.8371810913085938e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 7.3909759521484375e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 2.7848126888275146s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.2438507080078125e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.26793694496154785s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 8.344650268554688e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 2.8781700134277344s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 5.412101745605469e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.2780313491821289s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02109813690185547s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.3113021850585938e-05s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 2.867845058441162s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.1961669921875e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.24883055686950684s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.6702880859375e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 2.8425073623657227s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 5.6743621826171875e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.25412511825561523s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.765655517578125e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 8.821487426757812e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 2.8326516151428223s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 5.221366882324219e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.29468679428100586s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.020762920379638672s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 9.059906005859375e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.863720417022705s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.291534423828125e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.25266504287719727s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 8.106231689453125e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.7680201530456543s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.38690185546875e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2627558708190918s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.8371810913085938e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 8.106231689453125e-06s
INFO | --- Analysis for oxpoints took 2.8044707775115967s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.568826675415039s
Availability | VoID file availability check for Pali English Lexicon took 0.00031280517578125s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.2647891044616699s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.8848648071289062e-05s
Believability | Calculation of trust value for Pali English Lexicon took 7.152557373046875e-06s
INFO | --- Analysis for pali-english-lexicon took 5.683803558349609s
Availability | SPARQL endpoint availability check for PanLex took 4.172325134277344e-05s
Availability | VoID file availability check for PanLex took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for PanLex took 0.2483844757080078s
Reputation | Calculation of the PageRank for PanLex took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for PanLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PanLex took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.367134094238281e-05s
Believability | Calculation of trust value for PanLex took 7.62939453125e-06s
INFO | --- Analysis for panlex took 2.8396544456481934s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 4.124641418457031e-05s
Availability | VoID file availability check for patents.data.gov.uk took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.2512238025665283s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.649162292480469e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 8.344650268554688e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.9016528129577637s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.2438507080078125e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.000274658203125s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.2607154846191406s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.021872520446777344s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0009663105010986328s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 4.2438507080078125e-05s
Believability | Calculation of trust value for PDEV-Lemon took 8.821487426757812e-06s
INFO | --- Analysis for pdev-lemon took 2.8114359378814697s
Availability | SPARQL endpoint availability check for pdevlemon took 8.320808410644531e-05s
Availability | VoID file availability check for pdevlemon took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.28942012786865234s
Reputation | Calculation of the PageRank for pdevlemon took 0.020627975463867188s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.075599670410156e-05s
Believability | Calculation of trust value for pdevlemon took 1.1205673217773438e-05s
INFO | --- Analysis for pdevlemon took 2.8861701488494873s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.696846008300781e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.00038051605224609375s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.27846455574035645s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02069234848022461s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.939338684082031e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 8.821487426757812e-06s
INFO | --- Analysis for periodo took 2.9314982891082764s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.3392181396484375e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.2485663890838623s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0003826618194580078s
Believability | Calculation of trust value for Personal_Homepages took 8.106231689453125e-06s
INFO | --- Analysis for personal-homepages took 2.808149576187134s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 4.2438507080078125e-05s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.2533609867095947s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.409385681152344e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 8.58306884765625e-06s
INFO | --- Analysis for phoible took 2.849860191345215s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.482269287109375e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2766265869140625s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.440017700195312e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 9.5367431640625e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.9281370639801025s
Availability | SPARQL endpoint availability check for Pleiades took 4.3392181396484375e-05s
Availability | VoID file availability check for Pleiades took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Pleiades took 0.2666182518005371s
Reputation | Calculation of the PageRank for Pleiades took 0.021213293075561523s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.654594421386719e-05s
Believability | Calculation of trust value for Pleiades took 7.867813110351562e-06s
INFO | --- Analysis for pleiades took 2.8595333099365234s
Availability | SPARQL endpoint availability check for Poképédia took 4.506111145019531e-05s
Availability | VoID file availability check for Poképédia took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2676584720611572s
Reputation | Calculation of the PageRank for Poképédia took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Poképédia took 6.914138793945312e-05s
Believability | Calculation of trust value for Poképédia took 1.3589859008789062e-05s
INFO | --- Analysis for pokepedia-fr took 2.8210690021514893s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.410743713378906e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.00038361549377441406s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.26163339614868164s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.02153635025024414s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.726119995117188e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.344650268554688e-06s
INFO | --- Analysis for polymath-virtual-library took 2.801068067550659s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.291534423828125e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.23900961875915527s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 2.9325485229492188e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 7.62939453125e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.8065881729125977s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 5.793571472167969e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.26729869842529297s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 2.9087066650390625e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 8.58306884765625e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.9105021953582764s
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.0002961158752441406s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.27535247802734375s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 2.9087066650390625e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 8.344650268554688e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.913985013961792s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 7.414817810058594e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.0003428459167480469s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2911245822906494s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.0994415283203125e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 8.821487426757812e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.891928195953369s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 5.650520324707031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2650272846221924s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.02073383331298828s
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.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 9.298324584960938e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.9244515895843506s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.315376281738281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.000335693359375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.2479405403137207s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0010004043579101562s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.4809112548828125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 8.344650268554688e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.846048355102539s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.315376281738281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.24321389198303223s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 8.821487426757812e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.8216419219970703s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 6.818771362304688e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.27699804306030273s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 2.86102294921875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.8918039798736572s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.24781131744384766s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.504753112792969e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.9189536571502686s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.24499011039733887s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.799744129180908s
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.00022602081298828125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2629218101501465s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 9.059906005859375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.8272032737731934s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 7.891654968261719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.27045512199401855s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.021147727966308594s
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.0009813308715820312s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.337860107421875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.869965076446533s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 9.322166442871094e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.25845885276794434s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.02050328254699707s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0008220672607421875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.937042236328125s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.26782798767089844s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 1.1682510375976562e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.9184606075286865s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.4345855712890625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.23610138893127441s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 2.8848648071289062e-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.799062728881836s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2465381622314453s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.7179718017578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.823594570159912s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 5.054473876953125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.25409793853759766s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.8640658855438232s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.25786805152893066s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.8647351264953613s
Availability | SPARQL endpoint availability check for prefix.cc took 4.982948303222656e-05s
Availability | VoID file availability check for prefix.cc took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2438523769378662s
Reputation | Calculation of the PageRank for prefix.cc took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.5762786865234375e-05s
Believability | Calculation of trust value for prefix.cc took 1.3589859008789062e-05s
INFO | --- Analysis for prefix-cc took 2.819500684738159s
Availability | SPARQL endpoint availability check for PreLex took 4.2438507080078125e-05s
Availability | VoID file availability check for PreLex took 0.00032806396484375s
Completeness | Calculation of interlinking completeness for PreLex took 0.26357460021972656s
Reputation | Calculation of the PageRank for PreLex took 0.020923376083374023s
Interlinking | Calculation of Degree of Connection for PreLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.319450378417969e-05s
Believability | Calculation of trust value for PreLex took 7.867813110351562e-06s
INFO | --- Analysis for prelex took 2.8745980262756348s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.4022510051727295s
Availability | VoID file availability check for Prelinger Archives took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.27597594261169434s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.147125244140625e-05s
Believability | Calculation of trust value for Prelinger Archives took 7.3909759521484375e-06s
INFO | --- Analysis for prelinger_archives took 6.362452983856201s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 4.124641418457031e-05s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.2569446563720703s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 4.887580871582031e-05s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 7.3909759521484375e-06s
INFO | --- Analysis for premon took 2.858673572540283s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 7.724761962890625e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.26825737953186035s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.3882598876953125e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 8.106231689453125e-06s
INFO | --- Analysis for princeton-library-findingaids took 2.7852296829223633s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.6636021137237549s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.25786757469177246s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.20159912109375e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.58306884765625e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.545278310775757s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.267692565917969e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.2789597511291504s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.0040740966796875e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 7.867813110351562e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.8725948333740234s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.363059997558594e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.28885674476623535s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.02096867561340332s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0009791851043701172s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.457069396972656e-05s
Believability | Calculation of trust value for Procomún SPARQL took 8.106231689453125e-06s
INFO | --- Analysis for procomun-sparql took 2.9236350059509277s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.24697113037109375s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.0279159545898438e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 7.867813110351562e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.8333895206451416s
Availability | SPARQL endpoint availability check for ProductDB took 4.792213439941406e-05s
Availability | VoID file availability check for ProductDB took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for ProductDB took 0.24109625816345215s
Reputation | Calculation of the PageRank for ProductDB took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.271766662597656e-05s
Believability | Calculation of trust value for ProductDB took 1.049041748046875e-05s
INFO | --- Analysis for productdb took 2.744234085083008s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.23126602172851562s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 8.130073547363281e-05s
Believability | Calculation of trust value for Product Types Ontology took 8.58306884765625e-06s
INFO | --- Analysis for productontology took 2.7972562313079834s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.1484832763671875e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.25600457191467285s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020245075225830078s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 9.799003601074219e-05s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 2.8164658546447754s
Availability | SPARQL endpoint availability check for provenanceweb took 4.172325134277344e-05s
Availability | VoID file availability check for provenanceweb took 0.0002999305725097656s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.2611997127532959s
Reputation | Calculation of the PageRank for provenanceweb took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 6.818771362304688e-05s
Believability | Calculation of trust value for provenanceweb took 7.867813110351562e-06s
INFO | --- Analysis for provenanceweb took 2.8160204887390137s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 5.626678466796875e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2627418041229248s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0009558200836181641s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00011205673217773438s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.3113021850585938e-05s
INFO | --- Analysis for proyectoapadrina took 2.8486993312835693s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 4.1961669921875e-05s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.2722601890563965s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.123283386230469e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 1.2159347534179688e-05s
INFO | --- Analysis for pscs-catalogue took 2.9148643016815186s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.172325134277344e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.2719423770904541s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 6.866455078125e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 7.3909759521484375e-06s
INFO | --- Analysis for psh-subject-headings took 2.814826250076294s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.172325134277344e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.26511359214782715s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 2.7894973754882812e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 7.62939453125e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.8359453678131104s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 4.172325134277344e-05s
Availability | VoID file availability check for Public Spending in Greece took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.2754180431365967s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.022743940353393555s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0010900497436523438s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 9.679794311523438e-05s
Believability | Calculation of trust value for Public Spending in Greece took 8.344650268554688e-06s
INFO | --- Analysis for public-spending-in-greece took 2.864328384399414s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.1961669921875e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.24742603302001953s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.8133392333984375e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 6.9141387939453125e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.815948247909546s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 5.4836273193359375e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.24132204055786133s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.0040740966796875e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 7.3909759521484375e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 2.9155242443084717s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.315376281738281e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.25913429260253906s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 2.8371810913085938e-05s
Believability | Calculation of trust value for qualitywebdata.org took 8.106231689453125e-06s
INFO | --- Analysis for qualitywebdata-org took 2.857191801071167s
Availability | SPARQL endpoint availability check for Quotations Book took 4.1484832763671875e-05s
Availability | VoID file availability check for Quotations Book took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.2739255428314209s
Reputation | Calculation of the PageRank for Quotations Book took 0.02100968360900879s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 2.9325485229492188e-05s
Believability | Calculation of trust value for Quotations Book took 8.344650268554688e-06s
INFO | --- Analysis for quotations_book took 2.8600587844848633s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2549738883972168s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020821094512939453s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.62939453125e-06s
INFO | --- Analysis for r4r took 2.7728466987609863s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.23628020286560059s
Availability | VoID file availability check for Rådata nå! took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.26121068000793457s
Reputation | Calculation of the PageRank for Rådata nå! took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 7.963180541992188e-05s
Believability | Calculation of trust value for Rådata nå! took 7.152557373046875e-06s
INFO | --- Analysis for radatana took 3.077282667160034s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.5299530029296875e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.26188063621520996s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020721912384033203s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.6716461181640625e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 8.58306884765625e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 2.823932647705078s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.267692565917969e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.0003037452697753906s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.24013972282409668s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.02138042449951172s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.147125244140625e-05s
Believability | Calculation of trust value for Raphael Research Resource took 7.152557373046875e-06s
INFO | --- Analysis for raphaelresearchresource took 2.826930046081543s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 4.1484832763671875e-05s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.26576805114746094s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 2.9087066650390625e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 7.152557373046875e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 2.7911038398742676s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.3392181396484375e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.24395322799682617s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 2.8848648071289062e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 2.8118839263916016s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.2400221824645996s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.0517578125e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 2.840566873550415s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.458427429199219e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.27518367767333984s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.021033525466918945s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 2.8728792667388916s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.240631103515625s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.02098846435546875s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 2.8333170413970947s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.100799560546875e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.25226569175720215s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.218650817871094e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 8.344650268554688e-06s
INFO | --- Analysis for rcahmw-periods-list took 2.8554916381835938s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.124641418457031e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2765367031097412s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.20159912109375e-05s
Believability | Calculation of trust value for RDF Book Mashup took 7.152557373046875e-06s
INFO | --- Analysis for rdf-book-mashup took 2.8215620517730713s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.792213439941406e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2618281841278076s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010037422180175781s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 6.67572021484375e-06s
INFO | --- Analysis for rdfize-lastfm took 2.8123762607574463s
Availability | SPARQL endpoint availability check for RDFLicense took 4.00543212890625e-05s
Availability | VoID file availability check for RDFLicense took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.26191139221191406s
Reputation | Calculation of the PageRank for RDFLicense took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.0279159545898438e-05s
Believability | Calculation of trust value for RDFLicense took 6.67572021484375e-06s
INFO | --- Analysis for rdflicense took 2.858401298522949s
Availability | SPARQL endpoint availability check for RDFohloh took 4.172325134277344e-05s
Availability | VoID file availability check for RDFohloh took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.23778486251831055s
Reputation | Calculation of the PageRank for RDFohloh took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 8.749961853027344e-05s
Believability | Calculation of trust value for RDFohloh took 6.4373016357421875e-06s
INFO | --- Analysis for rdfohloh took 2.831281900405884s
Availability | SPARQL endpoint availability check for Reactome RDF took 4.2438507080078125e-05s
Availability | VoID file availability check for Reactome RDF took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.24276351928710938s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.6716461181640625e-05s
Believability | Calculation of trust value for Reactome RDF took 8.106231689453125e-06s
INFO | --- Analysis for reactome-rdf took 2.796924352645874s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 4.172325134277344e-05s
Availability | VoID file availability check for Rechtspraak.nl took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.2538580894470215s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.0207974910736084s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.369850158691406e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 7.62939453125e-06s
INFO | --- Analysis for rechtspraak took 2.8118600845336914s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.172325134277344e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.00039649009704589844s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.24248886108398438s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02097463607788086s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 9.34600830078125e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 9.059906005859375e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 2.8102800846099854s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 4.1961669921875e-05s
Availability | VoID file availability check for reference.data.gov.uk took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.24289369583129883s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015115737915039062s
Believability | Calculation of trust value for reference.data.gov.uk took 6.9141387939453125e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.7367055416107178s
Availability | SPARQL endpoint availability check for Regiony took 4.1961669921875e-05s
Availability | VoID file availability check for Regiony took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Regiony took 0.2649226188659668s
Reputation | Calculation of the PageRank for Regiony took 0.021061182022094727s
Interlinking | Calculation of Degree of Connection for Regiony took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Regiony took 2.8133392333984375e-05s
Believability | Calculation of trust value for Regiony took 6.198883056640625e-06s
INFO | --- Analysis for regiony took 2.7894279956817627s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.24471688270568848s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 3.409385681152344e-05s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 5.7220458984375e-06s
INFO | --- Analysis for reload took 2.824714422225952s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 4.029273986816406e-05s
Availability | VoID file availability check for Renewable Energy Generators took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.3199281692504883s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.1484832763671875e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 6.67572021484375e-06s
INFO | --- Analysis for renewable_energy_generators took 2.986607313156128s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 4.100799560546875e-05s
Availability | VoID file availability check for research.data.gov.uk took 0.00035953521728515625s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.2662959098815918s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.202957153320312e-05s
Believability | Calculation of trust value for research.data.gov.uk took 5.9604644775390625e-06s
INFO | --- Analysis for research-data-gov-uk took 2.846311092376709s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 6.008148193359375e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.24187445640563965s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.24249267578125e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 6.4373016357421875e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 2.8208255767822266s
Availability | SPARQL endpoint availability check for Restaurantes took 4.315376281738281e-05s
Availability | VoID file availability check for Restaurantes took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.24358677864074707s
Reputation | Calculation of the PageRank for Restaurantes took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 2.956390380859375e-05s
Believability | Calculation of trust value for Restaurantes took 6.198883056640625e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.7950429916381836s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.26325321197509766s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.866455078125e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 7.152557373046875e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 2.819352388381958s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 4.291534423828125e-05s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0004088878631591797s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.26271772384643555s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00013113021850585938s
Believability | Calculation of trust value for Revyu.com - Review Anything took 7.152557373046875e-06s
INFO | --- Analysis for revyu took 2.871040105819702s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.267692565917969e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.2637977600097656s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.6253204345703125e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 7.867813110351562e-06s
INFO | --- Analysis for riese took 2.8742377758026123s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.363059997558594e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.2507202625274658s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 6.67572021484375e-06s
INFO | --- Analysis for rijksmuseum took 2.7791595458984375s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 30.734359741210938s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.2880096435546875s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.76837158203125e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 8.344650268554688e-06s
INFO | --- Analysis for rism took 63.65821647644043s
Availability | SPARQL endpoint availability check for RISM Authority data took 20.11376929283142s
Availability | VoID file availability check for RISM Authority data took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.2711160182952881s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.3392181396484375e-05s
Believability | Calculation of trust value for RISM Authority data took 6.4373016357421875e-06s
INFO | --- Analysis for rism-authorities took 53.02276015281677s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 6.890296936035156e-05s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.2625718116760254s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.020680904388427734s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002257823944091797s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.830043077468872s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 4.076957702636719e-05s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.23939824104309082s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.020531415939331055s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00013446807861328125s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.7975196838378906s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.00033855438232421875s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2551746368408203s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.02089834213256836s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.0002117156982421875s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.8662192821502686s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 4.2438507080078125e-05s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.24985170364379883s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.02077960968017578s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.000156402587890625s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.8512895107269287s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 3.981590270996094e-05s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.26416683197021484s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015234947204589844s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.948178291320801s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 4.601478576660156e-05s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.257246732711792s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.528594970703125e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.806562900543213s
Availability | SPARQL endpoint availability check for crm took 4.1961669921875e-05s
Availability | VoID file availability check for crm took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for crm took 0.25594019889831543s
Reputation | Calculation of the PageRank for crm took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for crm took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for crm took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for crm took 2.9087066650390625e-05s
Believability | Calculation of trust value for crm took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.787565231323242s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 4.2438507080078125e-05s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2638282775878906s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.023234844207763672s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00013875961303710938s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.8286566734313965s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 5.5789947509765625e-05s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.26296305656433105s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.078315734863281e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.806938409805298s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 4.2438507080078125e-05s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.25165367126464844s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.020722150802612305s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002338886260986328s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.863875150680542s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.2502260208129883s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.224082946777344e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.7084383964538574s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 4.363059997558594e-05s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2791008949279785s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.179115295410156e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.86373233795166s
Availability | SPARQL endpoint availability check for digitaleconomy took 4.267692565917969e-05s
Availability | VoID file availability check for digitaleconomy took 0.00038170814514160156s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.2602236270904541s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.8133392333984375e-05s
Believability | Calculation of trust value for digitaleconomy took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.8497183322906494s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 6.246566772460938e-05s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2558858394622803s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00015306472778320312s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.8444719314575195s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.291534423828125e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2603325843811035s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020574092864990234s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.38690185546875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.8812637329101562s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.124641418457031e-05s
Availability | VoID file availability check for enaktingpsi took 0.0003120899200439453s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.2503499984741211s
Reputation | Calculation of the PageRank for enaktingpsi took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 2.8848648071289062e-05s
Believability | Calculation of trust value for enaktingpsi took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.817875385284424s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.2656819820404053s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.021763324737548828s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0012021064758300781s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00021195411682128906s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.8493552207946777s
Availability | SPARQL endpoint availability check for epsrc took 4.1484832763671875e-05s
Availability | VoID file availability check for epsrc took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for epsrc took 0.2646758556365967s
Reputation | Calculation of the PageRank for epsrc took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for epsrc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for epsrc took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.340576171875e-05s
Believability | Calculation of trust value for epsrc took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.8127355575561523s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 4.1961669921875e-05s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.23644423484802246s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020242691040039062s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.82012939453125e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-era took 2.7929329872131348s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 4.124641418457031e-05s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.24430418014526367s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010323524475097656s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.8692445755004883s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.1961669921875e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00048828125s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.28873562812805176s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.0040740966796875e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-foreign took 2.7609875202178955s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 7.534027099609375e-05s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.23323845863342285s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.02055501937866211s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.606910705566406e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.818655252456665s
Availability | SPARQL endpoint availability check for fun took 4.100799560546875e-05s
Availability | VoID file availability check for fun took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for fun took 0.2611722946166992s
Reputation | Calculation of the PageRank for fun took 0.020231008529663086s
Interlinking | Calculation of Degree of Connection for fun took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for fun took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for fun took 7.081031799316406e-05s
Believability | Calculation of trust value for fun took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.846395492553711s
Availability | SPARQL endpoint availability check for gdlc took 4.124641418457031e-05s
Availability | VoID file availability check for gdlc took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for gdlc took 0.2971212863922119s
Reputation | Calculation of the PageRank for gdlc took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for gdlc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.532669067382812e-05s
Believability | Calculation of trust value for gdlc took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.9626684188842773s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 5.316734313964844e-05s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.26540160179138184s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00010991096496582031s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.885528326034546s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2525448799133301s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00013303756713867188s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.836108684539795s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 4.363059997558594e-05s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.25453686714172363s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020374298095703125s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0001342296600341797s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-irit took 2.8582041263580322s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.23887944221496582s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.103515625e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.7686007022857666s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 4.0531158447265625e-05s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.2879207134246826s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.534027099609375e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.898196220397949s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.251476526260376s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.172325134277344e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 2.8493175506591797s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2646050453186035s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016164779663085938s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-kisti took 3.9177145957946777s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.2596862316131592s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.000141143798828125s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.8675029277801514s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2655355930328369s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02018117904663086s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.031990051269531e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.8443527221679688s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 4.1484832763671875e-05s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.2621901035308838s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015282630920410156s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.8019063472747803s
Availability | SPARQL endpoint availability check for notube took 4.076957702636719e-05s
Availability | VoID file availability check for notube took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for notube took 0.2664070129394531s
Reputation | Calculation of the PageRank for notube took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for notube took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for notube took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for notube took 4.220008850097656e-05s
Believability | Calculation of trust value for notube took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.797440767288208s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 8.96453857421875e-05s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.27591824531555176s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00012874603271484375s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.8121960163116455s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.24377036094665527s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015306472778320312s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.8702406883239746s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.1961669921875e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.26735901832580566s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.7894973754882812e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-opencyc took 2.8428874015808105s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.23910975456237793s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02027273178100586s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 8.296966552734375e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-os took 2.8115620613098145s
Availability | SPARQL endpoint availability check for photos took 4.172325134277344e-05s
Availability | VoID file availability check for photos took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for photos took 0.25623154640197754s
Reputation | Calculation of the PageRank for photos took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for photos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for photos took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for photos took 7.2479248046875e-05s
Believability | Calculation of trust value for photos took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.824218988418579s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 6.29425048828125e-05s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.2529318332672119s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011086463928222656s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.7682151794433594s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 4.124641418457031e-05s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.24630284309387207s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019359588623046875s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.839632272720337s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 4.100799560546875e-05s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.2487621307373047s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0001366138458251953s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.7643749713897705s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.27723240852355957s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.083747863769531e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.8416409492492676s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2627384662628174s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020876169204711914s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012159347534179688s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-roma took 2.9037747383117676s
Availability | SPARQL endpoint availability check for roni took 4.3392181396484375e-05s
Availability | VoID file availability check for roni took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for roni took 0.25540828704833984s
Reputation | Calculation of the PageRank for roni took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for roni took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for roni took 2.765655517578125e-05s
Believability | Calculation of trust value for roni took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.7907357215881348s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 4.124641418457031e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.26706600189208984s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00021982192993164062s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.806283712387085s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 4.2438507080078125e-05s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.2579500675201416s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010466575622558594s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.92653226852417s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 4.267692565917969e-05s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.26242542266845703s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.703636169433594e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.893397092819214s
Availability | SPARQL endpoint availability check for webconf took 4.267692565917969e-05s
Availability | VoID file availability check for webconf took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for webconf took 0.25609731674194336s
Reputation | Calculation of the PageRank for webconf took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for webconf took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for webconf took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010132789611816406s
Believability | Calculation of trust value for webconf took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-webconf took 2.8551113605499268s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 4.1961669921875e-05s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.2885012626647949s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 6.580352783203125e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-webscience took 3.0761256217956543s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2631676197052002s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002079010009765625s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-wiki took 3.015512228012085s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 4.1484832763671875e-05s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.24239802360534668s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.441375732421875e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.816124200820923s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.00543212890625e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.24808192253112793s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 2.7418136596679688e-05s
Believability | Calculation of trust value for RKB Explorer Data took 7.62939453125e-06s
INFO | --- Analysis for rkb_explorer_data took 2.8164424896240234s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.267692565917969e-05s
Availability | VoID file availability check for The Rosetta Project took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.2613041400909424s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.218650817871094e-05s
Believability | Calculation of trust value for The Rosetta Project took 8.106231689453125e-06s
INFO | --- Analysis for rosetta-project took 2.881852865219116s
Availability | SPARQL endpoint availability check for Rpm Find took 6.842613220214844e-05s
Availability | VoID file availability check for Rpm Find took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.25466060638427734s
Reputation | Calculation of the PageRank for Rpm Find took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.123283386230469e-05s
Believability | Calculation of trust value for Rpm Find took 8.821487426757812e-06s
INFO | --- Analysis for rpm_find took 2.8546502590179443s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.38690185546875e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.268756628036499s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.021337509155273438s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 7.176399230957031e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 8.344650268554688e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 2.927804946899414s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 5.507469177246094e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2537243366241455s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.176399230957031e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 7.3909759521484375e-06s
INFO | --- Analysis for rubentaelman took 2.863494634628296s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 7.319450378417969e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.27513718605041504s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02054119110107422s
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.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.296966552734375e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.3828277587890625e-05s
INFO | --- Analysis for rubenverborgh took 2.9206650257110596s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 5.245208740234375e-05s
Availability | VoID file availability check for Russian Universities Specialities took 0.00041556358337402344s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.25233960151672363s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 3.24249267578125e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.1920928955078125e-05s
INFO | --- Analysis for russian-universities-specialities took 2.841615676879883s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.315376281738281e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.2600383758544922s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 2.9802322387695312e-05s
Believability | Calculation of trust value for RuThes Cloud took 6.198883056640625e-06s
INFO | --- Analysis for ruthes took 2.866849899291992s
Availability | SPARQL endpoint availability check for RxNorm took 4.363059997558594e-05s
Availability | VoID file availability check for RxNorm took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for RxNorm took 0.23946595191955566s
Reputation | Calculation of the PageRank for RxNorm took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for RxNorm took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RxNorm took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.218650817871094e-05s
Believability | Calculation of trust value for RxNorm took 6.9141387939453125e-06s
INFO | --- Analysis for rxnorm took 2.7895967960357666s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.267692565917969e-05s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.2610745429992676s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.020966768264770508s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 2.8371810913085938e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 7.62939453125e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 2.855736017227173s
Availability | SPARQL endpoint availability check for SALDO took 4.220008850097656e-05s
Availability | VoID file availability check for SALDO took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for SALDO took 0.2896144390106201s
Reputation | Calculation of the PageRank for SALDO took 0.02093982696533203s
Interlinking | Calculation of Degree of Connection for SALDO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.0517578125e-05s
Believability | Calculation of trust value for SALDO took 8.58306884765625e-06s
INFO | --- Analysis for saldo took 2.8863775730133057s
Availability | SPARQL endpoint availability check for SALDO-RDF took 4.124641418457031e-05s
Availability | VoID file availability check for SALDO-RDF took 0.000385284423828125s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.25242090225219727s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.600120544433594e-05s
Believability | Calculation of trust value for SALDO-RDF took 7.867813110351562e-06s
INFO | --- Analysis for saldo-rdf took 2.767578601837158s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 4.267692565917969e-05s
Availability | VoID file availability check for SALDOM-RDF took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2598690986633301s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.02097177505493164s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.1444091796875e-05s
INFO | --- Analysis for saldom-rdf took 2.8506035804748535s
Availability | SPARQL endpoint availability check for sameAs.org took 4.172325134277344e-05s
Availability | VoID file availability check for sameAs.org took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.2564554214477539s
Reputation | Calculation of the PageRank for sameAs.org took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 2.86102294921875e-05s
Believability | Calculation of trust value for sameAs.org took 8.106231689453125e-06s
INFO | --- Analysis for sameas-org took 2.8654043674468994s
Availability | SPARQL endpoint availability check for sandrart.net took 4.4345855712890625e-05s
Availability | VoID file availability check for sandrart.net took 0.00035691261291503906s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.27124929428100586s
Reputation | Calculation of the PageRank for sandrart.net took 0.020364999771118164s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.628036499023438e-05s
Believability | Calculation of trust value for sandrart.net took 1.3113021850585938e-05s
INFO | --- Analysis for sandrart-net took 2.929425001144409s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 4.076957702636719e-05s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.24769854545593262s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 2.7179718017578125e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 7.152557373046875e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 2.8487634658813477s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 4.363059997558594e-05s
Availability | VoID file availability check for Santillana Guide Dataset took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.2604804039001465s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.020337820053100586s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 2.5272369384765625e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 8.106231689453125e-06s
INFO | --- Analysis for santillana_guide_dataset took 2.8455898761749268s
Availability | SPARQL endpoint availability check for schema.org took 4.076957702636719e-05s
Availability | VoID file availability check for schema.org took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for schema.org took 0.2531015872955322s
Reputation | Calculation of the PageRank for schema.org took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for schema.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.0517578125e-05s
Believability | Calculation of trust value for schema.org took 7.152557373046875e-06s
INFO | --- Analysis for schema-org took 2.828404426574707s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 4.124641418457031e-05s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.26657867431640625s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007038116455078125s
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 6.9141387939453125e-06s
INFO | --- Analysis for schemapedia took 2.803161382675171s
Availability | SPARQL endpoint availability check for scholarlydata took 4.124641418457031e-05s
Availability | VoID file availability check for scholarlydata took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.27741146087646484s
Reputation | Calculation of the PageRank for scholarlydata took 0.020328998565673828s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 2.9802322387695312e-05s
Believability | Calculation of trust value for scholarlydata took 7.867813110351562e-06s
INFO | --- Analysis for scholarlydata took 2.8491017818450928s
Availability | SPARQL endpoint availability check for Scholarometer took 4.2438507080078125e-05s
Availability | VoID file availability check for Scholarometer took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.23299336433410645s
Reputation | Calculation of the PageRank for Scholarometer took 0.020356178283691406s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.440017700195312e-05s
Believability | Calculation of trust value for Scholarometer took 6.4373016357421875e-06s
INFO | --- Analysis for scholarometer took 2.8700993061065674s
Availability | SPARQL endpoint availability check for Science Commons took 4.172325134277344e-05s
Availability | VoID file availability check for Science Commons took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Science Commons took 0.25191330909729004s
Reputation | Calculation of the PageRank for Science Commons took 0.020257949829101562s
Interlinking | Calculation of Degree of Connection for Science Commons took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Science Commons took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Science Commons took 2.765655517578125e-05s
Believability | Calculation of trust value for Science Commons took 1.0967254638671875e-05s
INFO | --- Analysis for science_commons took 2.7888576984405518s
Availability | SPARQL endpoint availability check for ScienceWise took 4.124641418457031e-05s
Availability | VoID file availability check for ScienceWise took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.25015687942504883s
Reputation | Calculation of the PageRank for ScienceWise took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 2.7418136596679688e-05s
Believability | Calculation of trust value for ScienceWise took 1.1920928955078125e-05s
INFO | --- Analysis for sciencewise took 2.7922420501708984s
Availability | SPARQL endpoint availability check for sears.com took 4.792213439941406e-05s
Availability | VoID file availability check for sears.com took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for sears.com took 0.25382351875305176s
Reputation | Calculation of the PageRank for sears.com took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for sears.com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.723403930664062e-05s
Believability | Calculation of trust value for sears.com took 8.58306884765625e-06s
INFO | --- Analysis for sears took 2.830955982208252s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.340576171875e-05s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.2752220630645752s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.082389831542969e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 7.3909759521484375e-06s
INFO | --- Analysis for sec-rdfabout took 2.878953218460083s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.2732551097869873s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020259857177734375s
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.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 7.748603820800781e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for secold took 2.776007890701294s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.100799560546875e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.2615630626678467s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.02067852020263672s
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.000701904296875s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.765655517578125e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 7.3909759521484375e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 2.8615734577178955s
Availability | SPARQL endpoint availability check for semanlink took 4.100799560546875e-05s
Availability | VoID file availability check for semanlink took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for semanlink took 0.25029611587524414s
Reputation | Calculation of the PageRank for semanlink took 0.020335912704467773s
Interlinking | Calculation of Degree of Connection for semanlink took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for semanlink took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001392364501953125s
Believability | Calculation of trust value for semanlink took 7.152557373046875e-06s
INFO | --- Analysis for semanlink took 2.9327025413513184s
Availability | SPARQL endpoint availability check for Semantic Library took 4.124641418457031e-05s
Availability | VoID file availability check for Semantic Library took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.26509594917297363s
Reputation | Calculation of the PageRank for Semantic Library took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 3.0040740966796875e-05s
Believability | Calculation of trust value for Semantic Library took 9.298324584960938e-06s
INFO | --- Analysis for semantic-library took 2.8201651573181152s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.172325134277344e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.25751566886901855s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 2.9325485229492188e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 5.9604644775390625e-06s
INFO | --- Analysis for semantic-profiling-network took 2.837768077850342s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 4.38690185546875e-05s
Availability | VoID file availability check for Semantic Universe Data took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.23908543586730957s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Semantic Universe Data took 8.344650268554688e-06s
INFO | --- Analysis for semantic-universe took 2.8898282051086426s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 5.030632019042969e-05s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2705233097076416s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011229515075683594s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 8.821487426757812e-06s
INFO | --- Analysis for semantic-web-dog-food took 2.849762439727783s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.363059997558594e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.25505852699279785s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.315376281738281e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.0967254638671875e-05s
INFO | --- Analysis for semantic-web-grundlagen took 2.849780321121216s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.1961669921875e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.26006436347961426s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 2.765655517578125e-05s
Believability | Calculation of trust value for semantic-web-journal took 1.0013580322265625e-05s
INFO | --- Analysis for semantic-web-journal took 2.812641143798828s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.291534423828125e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.24287056922912598s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.082389831542969e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 1.2159347534179688e-05s
INFO | --- Analysis for semantic-xbrl took 2.883185386657715s
Availability | SPARQL endpoint availability check for Semantic Bible took 6.246566772460938e-05s
Availability | VoID file availability check for Semantic Bible took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.2445690631866455s
Reputation | Calculation of the PageRank for Semantic Bible took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.0994415283203125e-05s
Believability | Calculation of trust value for Semantic Bible took 1.3113021850585938e-05s
INFO | --- Analysis for semantic_bible took 2.859994649887085s
Availability | SPARQL endpoint availability check for SemanticQuran took 4.076957702636719e-05s
Availability | VoID file availability check for SemanticQuran took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.2388749122619629s
Reputation | Calculation of the PageRank for SemanticQuran took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.367134094238281e-05s
Believability | Calculation of trust value for SemanticQuran took 7.3909759521484375e-06s
INFO | --- Analysis for semanticquran took 2.862295150756836s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.1961669921875e-05s
Availability | VoID file availability check for SemanticTweet took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.2513706684112549s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.364418029785156e-05s
Believability | Calculation of trust value for SemanticTweet took 6.67572021484375e-06s
INFO | --- Analysis for semantictweet took 2.8541908264160156s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.0531158447265625e-05s
Availability | VoID file availability check for semanticweb.org took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.2757387161254883s
Reputation | Calculation of the PageRank for semanticweb.org took 0.0212709903717041s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.963180541992188e-05s
Believability | Calculation of trust value for semanticweb.org took 7.152557373046875e-06s
INFO | --- Analysis for semanticweb-org took 2.864346981048584s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 4.57763671875e-05s
Availability | VoID file availability check for Semantic CrunchBase took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.2471771240234375s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.246566772460938e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 7.62939453125e-06s
INFO | --- Analysis for semsol-crunchbase took 2.770569324493408s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.220008850097656e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.2556638717651367s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020843505859375s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.000986337661743164s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.4332275390625e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 8.821487426757812e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.8501715660095215s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 6.771087646484375e-05s
Availability | VoID file availability check for SentimentWortschatz took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2681162357330322s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.0531158447265625e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.4066696166992188e-05s
INFO | --- Analysis for sentiws took 2.840257167816162s
Availability | SPARQL endpoint availability check for Serendipity took 4.1484832763671875e-05s
Availability | VoID file availability check for Serendipity took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Serendipity took 0.255603551864624s
Reputation | Calculation of the PageRank for Serendipity took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Serendipity took 6.747245788574219e-05s
Believability | Calculation of trust value for Serendipity took 1.2159347534179688e-05s
INFO | --- Analysis for serendipity took 2.921351194381714s
Availability | SPARQL endpoint availability check for Shoah victims? names took 4.267692565917969e-05s
Availability | VoID file availability check for Shoah victims? names took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.26530981063842773s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 3.6716461181640625e-05s
Believability | Calculation of trust value for Shoah victims? names took 7.3909759521484375e-06s
INFO | --- Analysis for shoah-victims-names took 2.8775007724761963s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.1484832763671875e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.0003275871276855469s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.27646565437316895s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 2.765655517578125e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 6.9141387939453125e-06s
INFO | --- Analysis for simile_data_collection took 2.876225471496582s
Availability | SPARQL endpoint availability check for SIMPLE took 4.5299530029296875e-05s
Availability | VoID file availability check for SIMPLE took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.2546675205230713s
Reputation | Calculation of the PageRank for SIMPLE took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for SIMPLE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 3.814697265625e-05s
Believability | Calculation of trust value for SIMPLE took 9.059906005859375e-06s
INFO | --- Analysis for simple took 2.86684250831604s
Availability | SPARQL endpoint availability check for SITC-V4 took 4.1484832763671875e-05s
Availability | VoID file availability check for SITC-V4 took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.2509312629699707s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02088022232055664s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.218650817871094e-05s
Believability | Calculation of trust value for SITC-V4 took 7.62939453125e-06s
INFO | --- Analysis for sitc-v4 took 2.945622205734253s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.1961669921875e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.24367308616638184s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 2.8133392333984375e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 2.2649765014648438e-05s
INFO | --- Analysis for slideshare2rdf took 2.837247133255005s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.1961669921875e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.2606501579284668s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 2.765655517578125e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 1.239776611328125e-05s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.8982772827148438s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 6.246566772460938e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.260361909866333s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 2.6464462280273438e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.1444091796875e-05s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.8097100257873535s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 4.38690185546875e-05s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.2537119388580322s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.218650817871094e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.2874603271484375e-05s
INFO | --- Analysis for smartlink took 2.8784677982330322s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.267692565917969e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00038909912109375s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.25668883323669434s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 2.9325485229492188e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 1.2874603271484375e-05s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 3.0222766399383545s
Availability | SPARQL endpoint availability check for SocialLink took 4.0531158447265625e-05s
Availability | VoID file availability check for SocialLink took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for SocialLink took 0.24411249160766602s
Reputation | Calculation of the PageRank for SocialLink took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for SocialLink took 2.8371810913085938e-05s
Believability | Calculation of trust value for SocialLink took 7.152557373046875e-06s
INFO | --- Analysis for sociallink took 2.776552438735962s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.2519657611846924s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.131431579589844e-05s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 2.8743979930877686s
Availability | SPARQL endpoint availability check for SORS took 4.267692565917969e-05s
Availability | VoID file availability check for SORS took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for SORS took 0.27351856231689453s
Reputation | Calculation of the PageRank for SORS took 0.020338058471679688s
Interlinking | Calculation of Degree of Connection for SORS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for SORS took 4.673004150390625e-05s
Believability | Calculation of trust value for SORS took 7.3909759521484375e-06s
INFO | --- Analysis for sors took 2.87174654006958s
Availability | SPARQL endpoint availability check for Soudy České republiky took 6.914138793945312e-05s
Availability | VoID file availability check for Soudy České republiky took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.2394726276397705s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 3.695487976074219e-05s
Believability | Calculation of trust value for Soudy České republiky took 6.198883056640625e-06s
INFO | --- Analysis for soudy--esk--republiky took 2.889230728149414s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.7206878662109375e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.000244140625s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.2566568851470947s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 0.000110626220703125s
Believability | Calculation of trust value for southampton-ac-uk took 7.3909759521484375e-06s
INFO | --- Analysis for southampton-ac-uk took 2.8377444744110107s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 4.220008850097656e-05s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.2657194137573242s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 8.106231689453125e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 2.9529242515563965s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.172325134277344e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2638425827026367s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 8.96453857421875e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.239776611328125e-05s
INFO | --- Analysis for southampton-ecs-eprints took 2.8358490467071533s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 4.100799560546875e-05s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.2770376205444336s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 2.9087066650390625e-05s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 8.344650268554688e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 2.9736289978027344s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 4.1484832763671875e-05s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.26467013359069824s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.458427429199219e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 7.62939453125e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.8845632076263428s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 5.6743621826171875e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0003533363342285156s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.2640647888183594s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 3.075599670410156e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 7.62939453125e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 2.823840618133545s
Availability | SPARQL endpoint availability check for SPQR took 4.220008850097656e-05s
Availability | VoID file availability check for SPQR took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for SPQR took 0.24816679954528809s
Reputation | Calculation of the PageRank for SPQR took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for SPQR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.7418136596679688e-05s
Believability | Calculation of trust value for SPQR took 1.3589859008789062e-05s
INFO | --- Analysis for spqr took 2.838374376296997s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.3392181396484375e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.27948689460754395s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 7.62939453125e-06s
INFO | --- Analysis for srcmf took 2.8671326637268066s
Availability | SPARQL endpoint availability check for SSF took 4.2438507080078125e-05s
Availability | VoID file availability check for SSF took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for SSF took 0.2446439266204834s
Reputation | Calculation of the PageRank for SSF took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for SSF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SSF took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for SSF took 2.86102294921875e-05s
Believability | Calculation of trust value for SSF took 8.106231689453125e-06s
INFO | --- Analysis for ssf-lexicon took 2.811582326889038s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 5.888938903808594e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.27501964569091797s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.4332275390625e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 7.3909759521484375e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.888730049133301s
Availability | SPARQL endpoint availability check for STAC took 4.220008850097656e-05s
Availability | VoID file availability check for STAC took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for STAC took 0.2906928062438965s
Reputation | Calculation of the PageRank for STAC took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for STAC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for STAC took 2.86102294921875e-05s
Believability | Calculation of trust value for STAC took 7.867813110351562e-06s
INFO | --- Analysis for stac took 2.8191239833831787s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.076957702636719e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.26928281784057617s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 2.86102294921875e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 7.152557373046875e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.830944299697876s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.291534423828125e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.2515115737915039s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.218650817871094e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 7.152557373046875e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 2.876291513442993s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 4.076957702636719e-05s
Availability | VoID file availability check for statistics.data.gov.uk took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2772843837738037s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010371208190917969s
Believability | Calculation of trust value for statistics.data.gov.uk took 7.62939453125e-06s
INFO | --- Analysis for statistics-data-gov-uk took 2.885716199874878s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 5.030632019042969e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.2546050548553467s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02064681053161621s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.9325485229492188e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 7.3909759521484375e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.864535093307495s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2648966312408447s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010180473327636719s
Believability | Calculation of trust value for statusnet-1w6-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-1w6-org took 2.806519031524658s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.26010656356811523s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 5.9604644775390625e-05s
Believability | Calculation of trust value for statusnet-20100-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-20100-org took 2.795048236846924s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0003154277801513672s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2782166004180908s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.800710678100586s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.2541391849517822s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 7.796287536621094e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.8797943592071533s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.25013160705566406s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 8.893013000488281e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.849965810775757s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.2535710334777832s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00010395050048828125s
Believability | Calculation of trust value for statusnet-bka-li took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-bka-li took 2.8821680545806885s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0003783702850341797s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.26139116287231445s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.719329833984375e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 2.781909465789795s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.24387550354003906s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.649162292480469e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ced117-net took 2.8007566928863525s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 5.602836608886719e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.265399694442749s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.14984130859375e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.8303136825561523s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.26314616203308105s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00010943412780761719s
Believability | Calculation of trust value for statusnet-chromic-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.807086944580078s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 5.459785461425781e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0003037452697753906s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.26395177841186523s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.486343383789062e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 2.8330845832824707s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.00035762786865234375s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.25289320945739746s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 4.9591064453125e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.8052854537963867s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 0.0005140304565429688s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2313992977142334s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 2.763319253921509s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2702324390411377s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 9.894371032714844e-05s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.8452937602996826s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.2728855609893799s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 5.888938903808594e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.8348398208618164s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.24895858764648438s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 4.8160552978515625e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-doomicile-de took 2.7863245010375977s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.24816322326660156s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.626678466796875e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-dtdns-net took 2.7778520584106445s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.24369502067565918s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.600120544433594e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.7877864837646484s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.24187421798706055s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 6.842613220214844e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-exdc-net took 2.7719125747680664s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.250262975692749s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 8.845329284667969e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-fcac-com took 2.89462947845459s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.27441883087158203s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020987987518310547s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 2.887821674346924s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.2445366382598877s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020307302474975586s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00017881393432617188s
Believability | Calculation of trust value for statusnet-fragdev-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-fragdev-com took 2.873196601867676s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.2457115650177002s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.7855775356292725s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.25086379051208496s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.02033090591430664s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010991096496582031s
Believability | Calculation of trust value for statusnet-gegeweb-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.8186612129211426s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.2749598026275635s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-glou-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-glou-org took 2.853322982788086s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2694549560546875s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.02089071273803711s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012540817260742188s
Believability | Calculation of trust value for statusnet-gomertronic-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.881404399871826s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.696846008300781e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2475574016571045s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020813703536987305s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00011086463928222656s
Believability | Calculation of trust value for statusnet-hackerposse-com took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.8314406871795654s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.792213439941406e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.00030040740966796875s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2644197940826416s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.6253204345703125e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-hii-co-il took 2.8114380836486816s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2630956172943115s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 8.988380432128906e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 2.902606964111328s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.27323102951049805s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 5.6743621826171875e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.844062328338623s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.8160552978515625e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2540934085845947s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.363059997558594e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-integralblue-com took 2.8984875679016113s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2751431465148926s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 7.62939453125e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 2.851038694381714s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2331836223602295s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.021472930908203125s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011992454528808594s
Believability | Calculation of trust value for statusnet-jonkman-ca took 7.62939453125e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 2.7551190853118896s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2505834102630615s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.512901306152344e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.91195011138916s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.25683093070983887s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.021322011947631836s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.863088369369507s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.26556897163391113s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.5762786865234375e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 2.8223319053649902s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.25066041946411133s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.853837013244629s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.27805542945861816s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.9114227294921875e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.846330404281616s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2530639171600342s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.809134006500244s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.26646852493286133s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.298324584960938e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.9226527214050293s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.2503058910369873s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011610984802246094s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.7857792377471924s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.26401257514953613s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-ludost-net took 2.812669277191162s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2629356384277344s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.632110595703125e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.8715527057647705s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.26444244384765625s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.078315734863281e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 2.8439719676971436s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2531876564025879s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014901161193847656s
Believability | Calculation of trust value for statusnet-macno-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-macno-org took 2.836479902267456s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.2515292167663574s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.7913594245910645s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.26668834686279297s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 7.557868957519531e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-maymay-net took 2.767920970916748s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.27501726150512695s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02028512954711914s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00015616416931152344s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.8576552867889404s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.26150012016296387s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.34600830078125e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.8657641410827637s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 5.078315734863281e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.27661991119384766s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.9119019508361816s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.27790021896362305s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.02031087875366211s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.895780563354492s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.25980234146118164s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02299809455871582s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00011014938354492188s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.851287841796875s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.25797271728515625s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.758059024810791s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.2761681079864502s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.808483600616455s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.26754093170166016s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.416175842285156e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.8460476398468018s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2594261169433594s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.02087688446044922s
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.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.696846008300781e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-panda-id-au took 2.820071220397949s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2656877040863037s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.021618127822875977s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.369850158691406e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.8951914310455322s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.24716854095458984s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.510185241699219e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.7900071144104004s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2579777240753174s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00023603439331054688s
Believability | Calculation of trust value for statusnet-postblue-info took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.7930145263671875s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 8.487701416015625e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2618272304534912s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020983457565307617s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.937980651855469e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-progval-net took 2.8721811771392822s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 5.626678466796875e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.272296667098999s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00012946128845214844s
Believability | Calculation of trust value for statusnet-qdnx-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.8555712699890137s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.26100969314575195s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 5.888938903808594e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-qth-fr took 2.840925693511963s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.24020767211914062s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020685434341430664s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021457672119140625s
Believability | Calculation of trust value for statusnet-quitter-se took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.807858943939209s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.2686781883239746s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010061264038085938s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.852954864501953s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.2545645236968994s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-recit-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-recit-org took 2.8775365352630615s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.27045249938964844s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00016546249389648438s
Believability | Calculation of trust value for statusnet-russwurm-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-russwurm-org took 2.841264247894287s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.25545573234558105s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020253658294677734s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 7.82012939453125e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-samnoble-org took 2.853966236114502s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.26484179496765137s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 7.82012939453125e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.8253839015960693s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2563025951385498s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02064657211303711s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.369850158691406e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.8952419757843018s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.24312806129455566s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.9065186977386475s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.25386834144592285s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 6.747245788574219e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 2.8402833938598633s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.2543368339538574s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.0002040863037109375s
Believability | Calculation of trust value for statusnet-skilledtests-com took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 2.855938673019409s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2573840618133545s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020392894744873047s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010037422180175781s
Believability | Calculation of trust value for statusnet-somsants-net took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.8422274589538574s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2588469982147217s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020221471786499023s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.0001289844512939453s
Believability | Calculation of trust value for statusnet-soucy-cc took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.852911949157715s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2530519962310791s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 5.6743621826171875e-05s
Believability | Calculation of trust value for statusnet-spip-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-spip-org took 2.829491376876831s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2563199996948242s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.8372507095336914s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.2623729705810547s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.021795272827148438s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00012683868408203125s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 2.7703750133514404s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.26645636558532715s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00021791458129882812s
Believability | Calculation of trust value for statusnet-status-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-status-net took 2.8151681423187256s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 5.555152893066406e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2443983554840088s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.7555317878723145s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 6.651878356933594e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.24208855628967285s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 8.678436279296875e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.8814144134521484s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.2665109634399414s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00013136863708496094s
Believability | Calculation of trust value for statusnet-thelovebug-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.858628511428833s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.00032591819763183594s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2552609443664551s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.152557373046875e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-thornton2-com took 3.0078694820404053s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.27056050300598145s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020682096481323242s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0008957386016845703s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00011873245239257812s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.8761303424835205s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2666604518890381s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.62396240234375e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-tl1n-com took 2.861823320388794s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2445974349975586s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.853742837905884s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2695345878601074s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.02055048942565918s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.647804260253906e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.8570330142974854s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.076957702636719e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.27968645095825195s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020319700241088867s
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.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.6464462280273438e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for steak took 2.8968842029571533s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.2438507080078125e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.2813854217529297s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0009505748748779297s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.984306335449219e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.239776611328125e-05s
INFO | --- Analysis for stitch-rameau took 2.8909106254577637s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.2438507080078125e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.2602367401123047s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020289182662963867s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 2.86102294921875e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 7.3909759521484375e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.7895009517669678s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 4.029273986816406e-05s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.25017547607421875s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00010538101196289062s
Believability | Calculation of trust value for STW Thesaurus for Economics took 7.3909759521484375e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 2.800144910812378s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 4.220008850097656e-05s
Availability | VoID file availability check for Sudoc bibliographic data took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.26207923889160156s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.363059997558594e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.2874603271484375e-05s
INFO | --- Analysis for sudocfr took 2.887295961380005s
Availability | SPARQL endpoint availability check for Surge Radio took 5.53131103515625e-05s
Availability | VoID file availability check for Surge Radio took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.2526726722717285s
Reputation | Calculation of the PageRank for Surge Radio took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 7.987022399902344e-05s
Believability | Calculation of trust value for Surge Radio took 6.198883056640625e-06s
INFO | --- Analysis for surge-radio took 2.8064069747924805s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.291534423828125e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.26636290550231934s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.341934204101562e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 7.62939453125e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 2.848879337310791s
Availability | SPARQL endpoint availability check for SweFN-RDF took 4.220008850097656e-05s
Availability | VoID file availability check for SweFN-RDF took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.26853227615356445s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for SweFN-RDF took 9.298324584960938e-06s
INFO | --- Analysis for swefn-rdf took 2.7803282737731934s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.124641418457031e-05s
Availability | VoID file availability check for SwetoDblp took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.24677371978759766s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.266334533691406e-05s
Believability | Calculation of trust value for SwetoDblp took 7.3909759521484375e-06s
INFO | --- Analysis for sweto-dblp took 2.8030948638916016s
Availability | SPARQL endpoint availability check for SymbolicData took 4.2438507080078125e-05s
Availability | VoID file availability check for SymbolicData took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.24051761627197266s
Reputation | Calculation of the PageRank for SymbolicData took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for SymbolicData took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 2.6464462280273438e-05s
Believability | Calculation of trust value for SymbolicData took 1.1920928955078125e-05s
INFO | --- Analysis for symbolicdata took 2.8282628059387207s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.40327930450439453s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.00026869773864746094s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4916648864746094s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.873051643371582s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 21.757094144821167s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 19.42768931388855s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.3804483413696289s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 4.345481634140015s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.12085294723510742s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 2.251702308654785s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.23985838890075684s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.1903214454650879s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.4230344295501709s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.205549001693726s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.6272506713867188s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 47.776583433151245s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3377535343170166s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.5629818439483643s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.1747431755065918s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.17864680290222168s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.790063858032227s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 3.314018249511719e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.4230942726135254s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.5860373973846436s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.4082555770874023s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.3283352851867676s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.3214941024780273s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 2.65419340133667s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.6064438819885254s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 69.19150280952454s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.1785423755645752s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.20592117309570312s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.1835775375366211s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2855100631713867s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0027594566345214844s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0023717880249023438s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.18451881408691406s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 48.247281312942505s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2624380588531494s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.595259189605713s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3086206912994385s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 48.43958497047424s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002232074737548828s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.478118896484375s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.17993855476379395s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 16.869903087615967s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.3220188617706299s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.430511474609375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 7.3909759521484375e-06s
INFO | --- Analysis for sztaki-lod took 754.7920970916748s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.291534423828125e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.25502586364746094s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020803213119506836s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.14984130859375e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 8.106231689453125e-06s
INFO | --- Analysis for t4gm-info took 2.836137294769287s
Availability | SPARQL endpoint availability check for tags2con delicious took 5.626678466796875e-05s
Availability | VoID file availability check for tags2con delicious took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.28551483154296875s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.220008850097656e-05s
Believability | Calculation of trust value for tags2con delicious took 8.58306884765625e-06s
INFO | --- Analysis for tags2con-delicious took 2.8635878562927246s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 4.1961669921875e-05s
Availability | VoID file availability check for Taiwan geographic names took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.24789166450500488s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.078315734863281e-05s
Believability | Calculation of trust value for Taiwan geographic names took 8.106231689453125e-06s
INFO | --- Analysis for taiwan-geographic-names took 2.888920307159424s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.38690185546875e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.2568397521972656s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 8.988380432128906e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.33514404296875e-05s
INFO | --- Analysis for talis-openlibrary took 4.0547308921813965s
Availability | SPARQL endpoint availability check for TalkBank took 4.291534423828125e-05s
Availability | VoID file availability check for TalkBank took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for TalkBank took 0.26851797103881836s
Reputation | Calculation of the PageRank for TalkBank took 0.020943880081176758s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for TalkBank took 3.266334533691406e-05s
Believability | Calculation of trust value for TalkBank took 8.821487426757812e-06s
INFO | --- Analysis for talkbank took 2.907130002975464s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 4.1484832763671875e-05s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.25273990631103516s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.02079606056213379s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00011968612670898438s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 8.821487426757812e-06s
INFO | --- Analysis for taxonconcept took 2.8549134731292725s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.1961669921875e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.25381016731262207s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 7.796287536621094e-05s
Believability | Calculation of trust value for taxonconcept-assets took 7.867813110351562e-06s
INFO | --- Analysis for taxonconcept-assets took 2.8165385723114014s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.1484832763671875e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0003185272216796875s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2560861110687256s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02090597152709961s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.054473876953125e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 8.344650268554688e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.868255853652954s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 4.124641418457031e-05s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.00034165382385253906s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.25736069679260254s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.673004150390625e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 8.106231689453125e-06s
INFO | --- Analysis for taxref-ld took 2.8063855171203613s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 8.869171142578125e-05s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.2638695240020752s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 2.9087066650390625e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 6.4373016357421875e-06s
INFO | --- Analysis for tcga took 2.7874157428741455s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 7.271766662597656e-05s
Availability | VoID file availability check for TCGA Roadmap took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.28328871726989746s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 6.771087646484375e-05s
Believability | Calculation of trust value for TCGA Roadmap took 6.4373016357421875e-06s
INFO | --- Analysis for tcga-roadmap took 2.885002374649048s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.26180100440979004s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020529747009277344s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 9.489059448242188e-05s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for tcmgenedit_dataset took 2.833224058151245s
Availability | SPARQL endpoint availability check for TDS took 4.9114227294921875e-05s
Availability | VoID file availability check for TDS took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for TDS took 0.26508235931396484s
Reputation | Calculation of the PageRank for TDS took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for TDS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TDS took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for TDS took 3.886222839355469e-05s
Believability | Calculation of trust value for TDS took 6.4373016357421875e-06s
INFO | --- Analysis for tds took 2.898118734359741s
Availability | SPARQL endpoint availability check for TED Talks took 4.124641418457031e-05s
Availability | VoID file availability check for TED Talks took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for TED Talks took 0.26399850845336914s
Reputation | Calculation of the PageRank for TED Talks took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for TED Talks took 2.956390380859375e-05s
Believability | Calculation of trust value for TED Talks took 1.1205673217773438e-05s
INFO | --- Analysis for ted-talks took 2.8384251594543457s
Availability | SPARQL endpoint availability check for TEKORD took 4.291534423828125e-05s
Availability | VoID file availability check for TEKORD took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2736337184906006s
Reputation | Calculation of the PageRank for TEKORD took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.2438507080078125e-05s
Believability | Calculation of trust value for TEKORD took 7.867813110351562e-06s
INFO | --- Analysis for tekord took 2.81453275680542s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 4.1961669921875e-05s
Availability | VoID file availability check for Telegraphis Linked Data took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.26490068435668945s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00010609626770019531s
Believability | Calculation of trust value for Telegraphis Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for telegraphis took 2.855609893798828s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.291534423828125e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.25601887702941895s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 6.699562072753906e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 6.4373016357421875e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 2.801923990249634s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 5.2928924560546875e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.24953556060791016s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.022641658782958984s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0008747577667236328s
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 8.821487426757812e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.9051403999328613s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.172325134277344e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2689635753631592s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.021530866622924805s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 2.8848648071289062e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 7.62939453125e-06s
INFO | --- Analysis for terminesp took 2.881446361541748s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 6.961822509765625e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.26556396484375s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 2.9087066650390625e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.152557373046875e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.807239055633545s
Availability | SPARQL endpoint availability check for Teseo took 4.124641418457031e-05s
Availability | VoID file availability check for Teseo took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Teseo took 0.2952134609222412s
Reputation | Calculation of the PageRank for Teseo took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for Teseo took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Teseo took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Teseo took 2.6702880859375e-05s
Believability | Calculation of trust value for Teseo took 7.867813110351562e-06s
INFO | --- Analysis for teseo took 2.907816171646118s
Availability | SPARQL endpoint availability check for xxxxx took 4.267692565917969e-05s
Availability | VoID file availability check for xxxxx took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for xxxxx took 0.24859309196472168s
Reputation | Calculation of the PageRank for xxxxx took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0008502006530761719s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.601478576660156e-05s
Believability | Calculation of trust value for xxxxx took 7.62939453125e-06s
INFO | --- Analysis for testee took 2.8361878395080566s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.2438507080078125e-05s
Availability | VoID file availability check for Texai Lexicon took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.2523069381713867s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 2.8133392333984375e-05s
Believability | Calculation of trust value for Texai Lexicon took 7.867813110351562e-06s
INFO | --- Analysis for texai_lexicon took 2.741391658782959s
Availability | SPARQL endpoint availability check for The CIARD RING took 8.940696716308594e-05s
Availability | VoID file availability check for The CIARD RING took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.28921961784362793s
Reputation | Calculation of the PageRank for The CIARD RING took 0.020392894744873047s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 2.8133392333984375e-05s
Believability | Calculation of trust value for The CIARD RING took 1.2159347534179688e-05s
INFO | --- Analysis for the-ciard-ring took 2.8790926933288574s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 4.9114227294921875e-05s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.26610898971557617s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.02073073387145996s
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.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.0040740966796875e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 8.106231689453125e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.9201364517211914s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.942969560623169s
Availability | VoID file availability check for The European Library Open Dataset took 0.0002570152282714844s
Extra | Recovery of all triples for The European Library Open Dataset took 1.1009681224822998s
Performance | Total latancy measurement for The European Library Open Dataset took 1.1896934509277344s
Amount of data | Number of triples check for The European Library Open Dataset took 30.209481477737427s
Versatility | Languages check for The European Library Open Dataset took 0.27234792709350586s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.22065782546997s
Interpretability | RDF structures check for The European Library Open Dataset took 0.24722957611083984s
Versatility | Serialization formats check for The European Library Open Dataset took 0.24917840957641602s
Availability | RDF dump link check for The European Library Open Dataset took 0.2240762710571289s
License | MR license check for The European Library Open Dataset took 0.23923778533935547s
License | HR license check for The European Library Open Dataset took 0.25960493087768555s
Amount of data | Number of property check for The European Library Open Dataset took 0.21814227104187012s
Understandability | Number of label check for The European Library Open Dataset took 0.5318772792816162s
Understandability | URI regex check for The European Library Open Dataset took 0.46507859230041504s
Understandability | Vocabs check for The European Library Open Dataset took 0.2512681484222412s
Verifiability | Authors check for The European Library Open Dataset took 0.23317408561706543s
Verifiability | Publishers check for The European Library Open Dataset took 0.23081302642822266s
Performance | Throughput check for The European Library Open Dataset took 11.58289623260498s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.414817810058594e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.23582220077514648s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.2741281986236572s
Interlinking | skos check for The European Library Open Dataset took 0.29635119438171387s
Interlinking | skos check for The European Library Open Dataset took 0.2748711109161377s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.22720074653625488s
Currency | Creation date check for The European Library Open Dataset took 0.516075611114502s
Currency | Modification date check for The European Library Open Dataset took 0.4931008815765381s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.50536823272705s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.28743934631347656s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 0.41565418243408203s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.027220726013183594s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02721881866455078s
Consistency | Disjoint class check for The European Library Open Dataset took 0.22592854499816895s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.415637731552124s
Consistency | Misplaced classes for The European Library Open Dataset took 0.3435544967651367s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.7197740077972412s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.347355604171753s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.53904891014099s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.031145334243774414s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.2327258586883545s
Security | Sign check for The European Library Open Dataset took 0.24210572242736816s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 13.643527030944824s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.336681604385376s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 4.76837158203125e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 7.152557373046875e-06s
INFO | --- Analysis for the-european-library-open-dataset took 388.9994411468506s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 6.771087646484375e-05s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.2783353328704834s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020273447036743164s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 9.417533874511719e-05s
Believability | Calculation of trust value for The Eurostat Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for the-eurostat-linked-data took 3.2612385749816895s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.601478576660156e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.2606484889984131s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 2.8371810913085938e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.3909759521484375e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 2.9010744094848633s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.315376281738281e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.2670254707336426s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 6.628036499023438e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 7.3909759521484375e-06s
INFO | --- Analysis for the-living-lod-cloud took 2.858050584793091s
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.00027871131896972656s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.2530395984649658s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 3.314018249511719e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 1.33514404296875e-05s
INFO | --- Analysis for the-midi-linked-data-cloud took 2.8824119567871094s
Availability | SPARQL endpoint availability check for The View From took 0.10773396492004395s
Availability | VoID file availability check for The View From took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for The View From took 0.2655212879180908s
Reputation | Calculation of the PageRank for The View From took 0.020386457443237305s
Interlinking | Calculation of Degree of Connection for The View From took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The View From took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for The View From took 7.987022399902344e-05s
Believability | Calculation of trust value for The View From took 7.62939453125e-06s
INFO | --- Analysis for the-view-from took 3.001659393310547s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.315376281738281e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.23467588424682617s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 2.7894973754882812e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 7.867813110351562e-06s
INFO | --- Analysis for thesaurus-bncf took 2.846783399581909s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.124641418457031e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2559990882873535s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 2.8848648071289062e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 8.344650268554688e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.8461568355560303s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 7.288488864898682s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.2644073963165283s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.020390987396240234s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.486343383789062e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 7.62939453125e-06s
INFO | --- Analysis for thesaurus-w took 11.686789989471436s
Availability | SPARQL endpoint availability check for theses.fr took 4.0531158447265625e-05s
Availability | VoID file availability check for theses.fr took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for theses.fr took 0.26538777351379395s
Reputation | Calculation of the PageRank for theses.fr took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for theses.fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for theses.fr took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.7206878662109375e-05s
Believability | Calculation of trust value for theses.fr took 7.152557373046875e-06s
INFO | --- Analysis for thesesfr took 2.7944881916046143s
Availability | SPARQL endpoint availability check for ThIST took 4.172325134277344e-05s
Availability | VoID file availability check for ThIST took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for ThIST took 0.2698829174041748s
Reputation | Calculation of the PageRank for ThIST took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for ThIST took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0009253025054931641s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.20159912109375e-05s
Believability | Calculation of trust value for ThIST took 7.152557373046875e-06s
INFO | --- Analysis for thist took 2.8146002292633057s
Availability | SPARQL endpoint availability check for TIP took 39.010528326034546s
Availability | VoID file availability check for TIP took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for TIP took 0.2739386558532715s
Reputation | Calculation of the PageRank for TIP took 0.02069377899169922s
Interlinking | Calculation of Degree of Connection for TIP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010824203491210938s
Believability | Calculation of trust value for TIP took 7.62939453125e-06s
INFO | --- Analysis for tip took 80.13400077819824s
Availability | SPARQL endpoint availability check for Tourpedia took 4.220008850097656e-05s
Availability | VoID file availability check for Tourpedia took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.27260518074035645s
Reputation | Calculation of the PageRank for Tourpedia took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.4332275390625e-05s
Believability | Calculation of trust value for Tourpedia took 7.3909759521484375e-06s
INFO | --- Analysis for tourpedia took 2.8635458946228027s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.2610917091369629s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.02027416229248047s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.0531158447265625e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for traditional-korean-medicine took 2.827406644821167s
Availability | SPARQL endpoint availability check for Traffic Scotland took 4.124641418457031e-05s
Availability | VoID file availability check for Traffic Scotland took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.25165510177612305s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020535707473754883s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.337860107421875e-05s
Believability | Calculation of trust value for Traffic Scotland took 7.62939453125e-06s
INFO | --- Analysis for traffic-scotland took 2.7271485328674316s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 4.982948303222656e-05s
Availability | VoID file availability check for Transparency International Linked Data took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.2567574977874756s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010514259338378906s
Believability | Calculation of trust value for Transparency International Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for transparency-linked-data took 2.8318357467651367s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 7.033348083496094e-05s
Availability | VoID file availability check for transport.data.gov.uk took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.26464223861694336s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.059906005859375e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 7.3909759521484375e-06s
INFO | --- Analysis for transport-data-gov-uk took 2.8427488803863525s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 4.410743713378906e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.24434471130371094s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 3.0040740966796875e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 1.2874603271484375e-05s
INFO | --- Analysis for transport-openuplabs took 2.7793192863464355s
Availability | SPARQL endpoint availability check for Twarql took 4.267692565917969e-05s
Availability | VoID file availability check for Twarql took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Twarql took 0.2726156711578369s
Reputation | Calculation of the PageRank for Twarql took 0.021045207977294922s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.842613220214844e-05s
Believability | Calculation of trust value for Twarql took 8.106231689453125e-06s
INFO | --- Analysis for twarql took 2.8666939735412598s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.172325134277344e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.2618699073791504s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.170967102050781e-05s
Believability | Calculation of trust value for TWC Data-gov took 1.33514404296875e-05s
INFO | --- Analysis for twc-data-gov took 2.856142997741699s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 4.291534423828125e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.28943705558776855s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.02064204216003418s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 3.075599670410156e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 1.2874603271484375e-05s
INFO | --- Analysis for twc-demos took 2.9081132411956787s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 4.2438507080078125e-05s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.2650153636932373s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020663976669311523s
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.0007178783416748047s
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 1.3589859008789062e-05s
INFO | --- Analysis for twc-healthdata took 2.823681592941284s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 7.104873657226562e-05s
Availability | VoID file availability check for Instance Hub (all) took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.2510225772857666s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.02092719078063965s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0010154247283935547s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 8.368492126464844e-05s
Believability | Calculation of trust value for Instance Hub (all) took 8.344650268554688e-06s
INFO | --- Analysis for twc-hub took 2.791855812072754s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 4.172325134277344e-05s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.26839661598205566s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00010132789611816406s
Believability | Calculation of trust value for IEEE VIS Source Data took 8.344650268554688e-06s
INFO | --- Analysis for twc-ieeevis took 2.8366971015930176s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.1961669921875e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.24690651893615723s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.020910024642944336s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 8.726119995117188e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 8.821487426757812e-06s
INFO | --- Analysis for twc-logd took 2.8500804901123047s
Availability | SPARQL endpoint availability check for twc-opendap took 4.3392181396484375e-05s
Availability | VoID file availability check for twc-opendap took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.24979448318481445s
Reputation | Calculation of the PageRank for twc-opendap took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 6.794929504394531e-05s
Believability | Calculation of trust value for twc-opendap took 7.867813110351562e-06s
INFO | --- Analysis for twc-opendap took 2.8336021900177s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 5.078315734863281e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.26291584968566895s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 3.0517578125e-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.9090750217437744s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 6.437301635742188e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.2724568843841553s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 3.170967102050781e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 8.106231689453125e-06s
INFO | --- Analysis for twitter-lids took 2.8701367378234863s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.9447376728057861s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.2453014850616455s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.020557880401611328s
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.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.172325134277344e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.3828277587890625e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 4.402363061904907s
Availability | SPARQL endpoint availability check for Uberblic.org took 4.267692565917969e-05s
Availability | VoID file availability check for Uberblic.org took 0.0003056526184082031s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.2655496597290039s
Reputation | Calculation of the PageRank for Uberblic.org took 0.02105093002319336s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010991096496582031s
Believability | Calculation of trust value for Uberblic.org took 8.344650268554688e-06s
INFO | --- Analysis for uberblic took 2.893982410430908s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 7.319450378417969e-05s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.24674296379089355s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.0001049041748046875s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for uis-linked-data took 2.9169626235961914s
Availability | SPARQL endpoint availability check for UK Legislation took 4.220008850097656e-05s
Availability | VoID file availability check for UK Legislation took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.2804298400878906s
Reputation | Calculation of the PageRank for UK Legislation took 0.021039247512817383s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 0.00010061264038085938s
Believability | Calculation of trust value for UK Legislation took 7.62939453125e-06s
INFO | --- Analysis for uk-legislation-api took 2.8925974369049072s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.1484832763671875e-05s
Availability | VoID file availability check for UK Postcodes took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.2345597743988037s
Reputation | Calculation of the PageRank for UK Postcodes took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.459785461425781e-05s
Believability | Calculation of trust value for UK Postcodes took 8.106231689453125e-06s
INFO | --- Analysis for uk-postcodes took 2.8044681549072266s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.1961669921875e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.25255250930786133s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020363569259643555s
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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00011849403381347656s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.2159347534179688e-05s
INFO | --- Analysis for umbel took 2.8355062007904053s
Availability | SPARQL endpoint availability check for UMTHES took 4.220008850097656e-05s
Availability | VoID file availability check for UMTHES took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for UMTHES took 0.2679734230041504s
Reputation | Calculation of the PageRank for UMTHES took 0.020666122436523438s
Interlinking | Calculation of Degree of Connection for UMTHES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UMTHES took 0.0009009838104248047s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.4345855712890625e-05s
Believability | Calculation of trust value for UMTHES took 7.152557373046875e-06s
INFO | --- Analysis for umthes took 2.8982226848602295s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 4.1484832763671875e-05s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.23250722885131836s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 2.7418136596679688e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 8.344650268554688e-06s
INFO | --- Analysis for un-hazardous-numbers took 2.7929131984710693s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 5.435943603515625e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2619755268096924s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020740747451782227s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for unesco-thesaurus took 2.8326563835144043s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2631795406341553s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 2.8848648071289062e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for unescothes took 2.8696725368499756s
Availability | SPARQL endpoint availability check for UniProt took 4.1484832763671875e-05s
Availability | VoID file availability check for UniProt took 0.0004134178161621094s
Completeness | Calculation of interlinking completeness for UniProt took 0.23917412757873535s
Reputation | Calculation of the PageRank for UniProt took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for UniProt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UniProt took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.57763671875e-05s
Believability | Calculation of trust value for UniProt took 7.152557373046875e-06s
INFO | --- Analysis for uniprot took 2.935600519180298s
Availability | SPARQL endpoint availability check for UniProt citations took 4.1484832763671875e-05s
Availability | VoID file availability check for UniProt citations took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.27846479415893555s
Reputation | Calculation of the PageRank for UniProt citations took 0.020123004913330078s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 2.6226043701171875e-05s
Believability | Calculation of trust value for UniProt citations took 1.239776611328125e-05s
INFO | --- Analysis for uniprot-citations took 2.8542075157165527s
Availability | SPARQL endpoint availability check for UniProt databases took 4.1961669921875e-05s
Availability | VoID file availability check for UniProt databases took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.2507205009460449s
Reputation | Calculation of the PageRank for UniProt databases took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for UniProt databases took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 2.8848648071289062e-05s
Believability | Calculation of trust value for UniProt databases took 7.3909759521484375e-06s
INFO | --- Analysis for uniprot-databases took 2.910870313644409s
Availability | SPARQL endpoint availability check for uniprot-metadata took 4.1961669921875e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.23772597312927246s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 5.745887756347656e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.4066696166992188e-05s
INFO | --- Analysis for uniprot-metadata took 2.8496644496917725s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 4.076957702636719e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.2651512622833252s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020456314086914062s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 2.765655517578125e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 7.152557373046875e-06s
INFO | --- Analysis for uniprot-taxonomy took 2.8790388107299805s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.3392181396484375e-05s
Availability | VoID file availability check for UniProt UniParc took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.26418519020080566s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.021906614303588867s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 3.147125244140625e-05s
Believability | Calculation of trust value for UniProt UniParc took 7.62939453125e-06s
INFO | --- Analysis for uniprot-uniparc took 2.8969311714172363s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.100799560546875e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.24770474433898926s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 2.9325485229492188e-05s
Believability | Calculation of trust value for UniProt UniPathway took 7.62939453125e-06s
INFO | --- Analysis for uniprot-unipathway took 2.8988499641418457s
Availability | SPARQL endpoint availability check for UniProtKB took 4.076957702636719e-05s
Availability | VoID file availability check for UniProtKB took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.26131105422973633s
Reputation | Calculation of the PageRank for UniProtKB took 0.02069830894470215s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 5.364418029785156e-05s
Believability | Calculation of trust value for UniProtKB took 1.1682510375976562e-05s
INFO | --- Analysis for uniprotkb took 2.8811888694763184s
Availability | SPARQL endpoint availability check for UniProt UniRef took 4.2438507080078125e-05s
Availability | VoID file availability check for UniProt UniRef took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.265796422958374s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 3.743171691894531e-05s
Believability | Calculation of trust value for UniProt UniRef took 8.344650268554688e-06s
INFO | --- Analysis for uniref took 2.8166143894195557s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 4.220008850097656e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.273221492767334s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0207674503326416s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0008256435394287109s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 3.1948089599609375e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 7.152557373046875e-06s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 2.9025402069091797s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 4.267692565917969e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.2617971897125244s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 2.8848648071289062e-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 2.8107595443725586s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0002999305725097656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.25022459030151367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 2.891551971435547s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.2741518020629883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 2.8938777446746826s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.25378894805908203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 2.8927416801452637s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.24778223037719727s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 2.8933467864990234s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 5.435943603515625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.2404768466949463s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 2.8080239295959473s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.26244521141052246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.020461082458496094s
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.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 2.8278095722198486s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 5.173683166503906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.2754690647125244s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 2.848463296890259s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.2650754451751709s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 2.8294196128845215s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.2541379928588867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 2.8538970947265625s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.23886823654174805s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 4.649162292480469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech took 2.868140935897827s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 7.700920104980469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.2596886157989502s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.02058863639831543s
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.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 2.831031322479248s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.2547755241394043s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 2.8016343116760254s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2648129463195801s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-danish took 2.8785316944122314s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.26933813095092773s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 3.552436828613281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 2.8201208114624023s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.26867079734802246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 2.8695130348205566s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.2421858310699463s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.02057933807373047s
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.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 2.815812826156616s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.2796752452850342s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 2.8528501987457275s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 4.839897155761719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.2470717430114746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.021144628524780273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0010025501251220703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.76837158203125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 2.798081398010254s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.25868725776672363s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 2.9208765029907227s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.252826452255249s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 2.767751693725586s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.26355814933776855s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 2.836203098297119s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 0.00010156631469726562s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.2373201847076416s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-french took 2.852900266647339s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.259082555770874s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.020461320877075195s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 2.8217334747314453s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.000244140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.26757097244262695s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 2.7898848056793213s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 5.173683166503906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.2502148151397705s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02052760124206543s
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.000701904296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 2.8682138919830322s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.2487804889678955s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0009541511535644531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 5.221366882324219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 2.8767685890197754s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.27670741081237793s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 2.821861505508423s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 5.91278076171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.24250316619873047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 2.817384719848633s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.23295903205871582s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 2.795591115951538s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 6.842613220214844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.2887732982635498s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 2.9317870140075684s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 8.702278137207031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.2622807025909424s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 2.905363082885742s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.2531867027282715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-irish took 2.8481366634368896s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.2614879608154297s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020197391510009766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 2.9048941135406494s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.2668576240539551s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 2.81140398979187s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.2681868076324463s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 2.930306911468506s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.24707436561584473s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.02031254768371582s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 2.8852193355560303s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.23703765869140625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 2.759958267211914s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.26651787757873535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 2.847598075866699s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.25563526153564453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 2.817650079727173s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.24787020683288574s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 2.8758432865142822s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.24127197265625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.02060532569885254s
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.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 2.8311805725097656s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.24114751815795898s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 2.819488286972046s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.2735307216644287s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.020457983016967773s
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.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 2.8139660358428955s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.2599818706512451s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 2.849612236022949s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.261491060256958s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 2.8258872032165527s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.2635223865509033s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 2.8404417037963867s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.26337718963623047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020724058151245117s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 2.8401541709899902s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.00039505958557128906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.26465725898742676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 2.8759357929229736s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 6.151199340820312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.26082801818847656s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 2.8853719234466553s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.2613675594329834s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.02089381217956543s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 2.8331310749053955s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.2534201145172119s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 2.8719241619110107s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.8160552978515625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0003566741943359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.273773193359375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.020895719528198242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 2.910841941833496s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.26165175437927246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020836353302001953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 2.8566672801971436s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.2677171230316162s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 2.8160152435302734s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.2594633102416992s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 2.8974504470825195s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 5.412101745605469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.24862384796142578s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 2.85541033744812s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.27536463737487793s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 2.8093132972717285s
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.0003876686096191406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.23482894897460938s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 2.8218560218811035s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.00011801719665527344s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.2705221176147461s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 2.8354880809783936s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.24468612670898438s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 2.7378296852111816s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.23453521728515625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 5.984306335449219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 2.7623283863067627s
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.000255584716796875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.24004125595092773s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020920753479003906s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 2.7604684829711914s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.2673218250274658s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 2.7941102981567383s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.2303318977355957s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 2.7395577430725098s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.291534423828125e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.25686192512512207s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.747245788574219e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 5.9604644775390625e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 2.7649598121643066s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 4.267692565917969e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.24906587600708008s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 2.9087066650390625e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 1.239776611328125e-05s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 2.904005765914917s
Availability | SPARQL endpoint availability check for University of Bristol took 5.14984130859375e-05s
Availability | VoID file availability check for University of Bristol took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.2932906150817871s
Reputation | Calculation of the PageRank for University of Bristol took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.0040740966796875e-05s
Believability | Calculation of trust value for University of Bristol took 7.3909759521484375e-06s
INFO | --- Analysis for university-of-bristol took 2.929295063018799s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.267692565917969e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.2651815414428711s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.9591064453125e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 7.3909759521484375e-06s
INFO | --- Analysis for university-plymouth-reading-lists took 2.796144485473633s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.124641418457031e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.29846739768981934s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.4332275390625e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 8.106231689453125e-06s
INFO | --- Analysis for university-sussex-reading-lists took 2.9359397888183594s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 4.124641418457031e-05s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.2615678310394287s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 6.794929504394531e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 7.3909759521484375e-06s
INFO | --- Analysis for unodc took 2.9132163524627686s
Availability | SPARQL endpoint availability check for URIBurner took 4.124641418457031e-05s
Availability | VoID file availability check for URIBurner took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for URIBurner took 0.25151681900024414s
Reputation | Calculation of the PageRank for URIBurner took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for URIBurner took 9.799003601074219e-05s
Believability | Calculation of trust value for URIBurner took 1.2874603271484375e-05s
INFO | --- Analysis for uriburner took 2.829448938369751s
Availability | SPARQL endpoint availability check for US Political Violence took 4.3392181396484375e-05s
Availability | VoID file availability check for US Political Violence took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.24039983749389648s
Reputation | Calculation of the PageRank for US Political Violence took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for US Political Violence took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.0994415283203125e-05s
Believability | Calculation of trust value for US Political Violence took 7.152557373046875e-06s
INFO | --- Analysis for us-political-violence took 2.7501771450042725s
Availability | SPARQL endpoint availability check for USAGE review corpus took 4.124641418457031e-05s
Availability | VoID file availability check for USAGE review corpus took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.2614555358886719s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 2.956390380859375e-05s
Believability | Calculation of trust value for USAGE review corpus took 7.3909759521484375e-06s
INFO | --- Analysis for usage-review-corpus took 2.840721368789673s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 4.291534423828125e-05s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.25101613998413086s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.021752595901489258s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 8.630752563476562e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for utpl-lod took 2.7943949699401855s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 4.315376281738281e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.2600231170654297s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 2.8371810913085938e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 1.239776611328125e-05s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 2.868644952774048s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 4.2438507080078125e-05s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.25137972831726074s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.559226989746094e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 7.3909759521484375e-06s
INFO | --- Analysis for verrijktkoninkrijk took 2.7776191234588623s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 4.38690185546875e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.2620723247528076s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00017118453979492188s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 8.106231689453125e-06s
INFO | --- Analysis for viaf took 2.8274149894714355s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 7.2479248046875e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.2749037742614746s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 7.867813110351562e-06s
INFO | --- Analysis for vias-publicas-zaragoza took 2.9372546672821045s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 4.38690185546875e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.2447054386138916s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.020479679107666016s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 3.0517578125e-05s
Believability | Calculation of trust value for vimeo.videoobject took 7.3909759521484375e-06s
INFO | --- Analysis for vimeo_videoobject took 2.7578048706054688s
Availability | SPARQL endpoint availability check for VIVO took 4.267692565917969e-05s
Availability | VoID file availability check for VIVO took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for VIVO took 0.26628541946411133s
Reputation | Calculation of the PageRank for VIVO took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.937980651855469e-05s
Believability | Calculation of trust value for VIVO took 7.152557373046875e-06s
INFO | --- Analysis for vivo took 2.869905710220337s
Availability | SPARQL endpoint availability check for VIVO Cornell took 6.937980651855469e-05s
Availability | VoID file availability check for VIVO Cornell took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.25444817543029785s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.58306884765625e-05s
Believability | Calculation of trust value for VIVO Cornell took 8.344650268554688e-06s
INFO | --- Analysis for vivo-cornell-university took 2.9152331352233887s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 4.363059997558594e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.25804829597473145s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 3.075599670410156e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 7.3909759521484375e-06s
INFO | --- Analysis for vivo-cu-boulder took 2.791731595993042s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.220008850097656e-05s
Availability | VoID file availability check for VIVO Indiana took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.25005149841308594s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.025434017181396484s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.296966552734375e-05s
Believability | Calculation of trust value for VIVO Indiana took 6.67572021484375e-06s
INFO | --- Analysis for vivo-indiana-university took 2.8008549213409424s
Availability | SPARQL endpoint availability check for VIVO Ponce took 4.1961669921875e-05s
Availability | VoID file availability check for VIVO Ponce took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.2594034671783447s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.24249267578125e-05s
Believability | Calculation of trust value for VIVO Ponce took 6.9141387939453125e-06s
INFO | --- Analysis for vivo-ponce took 2.8038270473480225s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 4.100799560546875e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.23882365226745605s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.022154808044433594s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.62396240234375e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 8.106231689453125e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 2.790032148361206s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.291534423828125e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.23584604263305664s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.512901306152344e-05s
Believability | Calculation of trust value for VIVO University of Florida took 7.152557373046875e-06s
INFO | --- Analysis for vivo-university-of-florida took 2.7792770862579346s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 9.298324584960938e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.24737811088562012s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.62396240234375e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 8.106231689453125e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.729215383529663s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.100799560546875e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.277402400970459s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.552436828613281e-05s
Believability | Calculation of trust value for VIVO WUSTL took 7.3909759521484375e-06s
INFO | --- Analysis for vivo-wustl took 2.8001699447631836s
Availability | SPARQL endpoint availability check for vivo2doi took 4.220008850097656e-05s
Availability | VoID file availability check for vivo2doi took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.24955415725708008s
Reputation | Calculation of the PageRank for vivo2doi took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for vivo2doi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for vivo2doi took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.00543212890625e-05s
Believability | Calculation of trust value for vivo2doi took 7.62939453125e-06s
INFO | --- Analysis for vivo2doi took 2.8116800785064697s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.100799560546875e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.24630212783813477s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.0203702449798584s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.699562072753906e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 7.3909759521484375e-06s
INFO | --- Analysis for vu-wordnet took 2.8570046424865723s
Availability | SPARQL endpoint availability check for vulnerapedia took 4.172325134277344e-05s
Availability | VoID file availability check for vulnerapedia took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.3252379894256592s
Reputation | Calculation of the PageRank for vulnerapedia took 0.0202484130859375s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.4849853515625e-05s
Believability | Calculation of trust value for vulnerapedia took 7.867813110351562e-06s
INFO | --- Analysis for vulnerapedia took 2.9808104038238525s
Availability | SPARQL endpoint availability check for W3C took 5.340576171875e-05s
Availability | VoID file availability check for W3C took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for W3C took 0.23928546905517578s
Reputation | Calculation of the PageRank for W3C took 0.02069711685180664s
Interlinking | Calculation of Degree of Connection for W3C took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00016069412231445312s
Believability | Calculation of trust value for W3C took 7.867813110351562e-06s
INFO | --- Analysis for w3c took 2.780540704727173s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.458427429199219e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.24570202827453613s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 3.0517578125e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 1.1682510375976562e-05s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.78474760055542s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.172325134277344e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.2600393295288086s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00010895729064941406s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 7.3909759521484375e-06s
INFO | --- Analysis for w3c-wordnet took 2.837923288345337s
Availability | SPARQL endpoint availability check for WarSampo took 0.32999324798583984s
Availability | VoID file availability check for WarSampo took 0.0002911090850830078s
Extra | Recovery of all triples for WarSampo took 24.483829259872437s
Performance | Total latancy measurement for WarSampo took 0.8371336460113525s
Amount of data | Number of triples check for WarSampo took 18.767261266708374s
Interoperability | New terms check for WarSampo took 3.881462574005127s
Versatility | Languages check for WarSampo took 49.57281684875488s
Interpretability | Number of blank nodes check for WarSampo took 17.18190908432007s
Security | Check HTTPS for WarSampo took 0.4247722625732422s
Interpretability | RDF structures check for WarSampo took 0.1730635166168213s
Versatility | Serialization formats check for WarSampo took 0.1793355941772461s
Availability | RDF dump link check for WarSampo took 1.1898159980773926s
License | MR license check for WarSampo took 0.18323302268981934s
License | HR license check for WarSampo took 43.221452713012695s
Amount of data | Number of property check for WarSampo took 0.16224002838134766s
Understandability | Number of label check for WarSampo took 8.534262895584106s
Understandability | URI regex check for WarSampo took 0.3346061706542969s
Understandability | Vocabs check for WarSampo took 0.17533159255981445s
Verifiability | Authors check for WarSampo took 0.17400908470153809s
Verifiability | Publishers check for WarSampo took 0.18274688720703125s
Performance | Throughput check for WarSampo took 11.135287523269653s
Amount of data | Check the number of entities for WarSampo took 15.140872955322266s
Verifiability | Contribs. check for WarSampo took 0.17783594131469727s
Interlinking | sameAs chians check for WarSampo took 0.18086028099060059s
Interlinking | skos check for WarSampo took 0.1842660903930664s
Interlinking | skos check for WarSampo took 0.17504525184631348s
Timeliness | dataset update frequency check for WarSampo took 0.17610979080200195s
Currency | Creation date check for WarSampo took 0.33991479873657227s
Currency | Modification date check for WarSampo took 0.37570762634277344s
Rep.Conc. | URIs length for WarSampo took 48.488218545913696s
Interoperability | New vocabularies check for WarSampo took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.16713666915893555s
Accuracy | Check Functional Property for WarSampo took 0.1881544589996338s
Accuracy | Check Inverse Functional Property for WarSampo took 0.17880773544311523s
Accuracy | Check Empty annotation labels for WarSampo took 11.054214239120483s
Accuracy | Check White space in annotation for WarSampo took 2.2096478939056396s
Accuracy | Check Datatype consistency for WarSampo took 5.298612594604492s
Consistency | Disjoint class check for WarSampo took 0.17395472526550293s
Consistency | Check Misplaced properties for WarSampo took 19.91254186630249s
Consistency | Check Ontology hijacking for WarSampo took 18.96487259864807s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.4347951412200928s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.7227747440338135s
Conciseness | Check Extensional conciseness for WarSampo took 2.8462538719177246s
Conciseness | Check Intensional conciseness for WarSampo took 0.25713014602661133s
Security | Sign check for WarSampo took 0.16632819175720215s
Availability | Check URIs Dereferenciability for WarSampo took 2.759051561355591s
Completeness | Calculation of interlinking completeness for WarSampo took 0.9776763916015625s
Reputation | Calculation of the PageRank for WarSampo took 0.02094435691833496s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for WarSampo took 0.00010132789611816406s
Interoperability | Check the re-using of existing vocabs for WarSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for WarSampo took 8.821487426757812e-06s
INFO | --- Analysis for warsampo took 944.2389597892761s
Availability | SPARQL endpoint availability check for WebIsALOD took 4.1961669921875e-05s
Availability | VoID file availability check for WebIsALOD took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.2515711784362793s
Reputation | Calculation of the PageRank for WebIsALOD took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 7.43865966796875e-05s
Believability | Calculation of trust value for WebIsALOD took 8.106231689453125e-06s
INFO | --- Analysis for webisalod took 2.9048678874969482s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.220008850097656e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.2609381675720215s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.02089524269104004s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 4.363059997558594e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.3113021850585938e-05s
INFO | --- Analysis for webnmasunotraveler took 2.86741042137146s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 4.315376281738281e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.27475953102111816s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 6.794929504394531e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 7.867813110351562e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 2.844367504119873s
Availability | SPARQL endpoint availability check for WikiPathways took 4.172325134277344e-05s
Availability | VoID file availability check for WikiPathways took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.25738954544067383s
Reputation | Calculation of the PageRank for WikiPathways took 0.020531892776489258s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.9802322387695312e-05s
Believability | Calculation of trust value for WikiPathways took 7.3909759521484375e-06s
INFO | --- Analysis for wikipathways took 2.7970151901245117s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 4.076957702636719e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.2574753761291504s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 9.059906005859375e-06s
INFO | --- Analysis for wikiword_thesaurus took 2.8390092849731445s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 4.2438507080078125e-05s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.2546660900115967s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.020531415939331055s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.416175842285156e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.0967254638671875e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 2.810746669769287s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 4.315376281738281e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0003724098205566406s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.26334309577941895s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 8.344650268554688e-06s
INFO | --- Analysis for wings-workflow-provenance-dataset took 2.838691473007202s
Availability | SPARQL endpoint availability check for World Loanword Database took 4.363059997558594e-05s
Availability | VoID file availability check for World Loanword Database took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.27857089042663574s
Reputation | Calculation of the PageRank for World Loanword Database took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.081031799316406e-05s
Believability | Calculation of trust value for World Loanword Database took 7.3909759521484375e-06s
INFO | --- Analysis for wold took 2.827275037765503s
Availability | SPARQL endpoint availability check for Wordnet took 4.172325134277344e-05s
Availability | VoID file availability check for Wordnet took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Wordnet took 0.2502143383026123s
Reputation | Calculation of the PageRank for Wordnet took 0.020635366439819336s
Interlinking | Calculation of Degree of Connection for Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wordnet took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Wordnet took 4.00543212890625e-05s
Believability | Calculation of trust value for Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for wordnet took 2.8354320526123047s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.482269287109375e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.265897274017334s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 8.7738037109375e-05s
Believability | Calculation of trust value for WordNet-RDF took 5.9604644775390625e-06s
INFO | --- Analysis for wordnet-rdf took 2.8623058795928955s
Availability | SPARQL endpoint availability check for wordpress took 4.363059997558594e-05s
Availability | VoID file availability check for wordpress took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for wordpress took 0.25418543815612793s
Reputation | Calculation of the PageRank for wordpress took 0.021160602569580078s
Interlinking | Calculation of Degree of Connection for wordpress took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for wordpress took 0.00104522705078125s
Interlinking | Calculation of Clustering coefficient for wordpress took 0.00010704994201660156s
Believability | Calculation of trust value for wordpress took 8.58306884765625e-06s
INFO | --- Analysis for wordpress took 2.8551294803619385s
Availability | SPARQL endpoint availability check for wordpress.post took 4.220008850097656e-05s
Availability | VoID file availability check for wordpress.post took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.26219868659973145s
Reputation | Calculation of the PageRank for wordpress.post took 0.020646333694458008s
Interlinking | Calculation of Degree of Connection for wordpress.post took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for wordpress.post took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 2.8848648071289062e-05s
Believability | Calculation of trust value for wordpress.post took 1.2874603271484375e-05s
INFO | --- Analysis for wordpress_post took 2.9568939208984375s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 4.1484832763671875e-05s
Availability | VoID file availability check for World Bank Linked Data took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.2598738670349121s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012350082397460938s
Believability | Calculation of trust value for World Bank Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for world-bank-linked-data took 2.8478050231933594s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 7.915496826171875e-05s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.2379317283630371s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.678436279296875e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.3589859008789062e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 2.8266305923461914s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 5.2928924560546875e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.25441694259643555s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.821487426757812e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 1.0967254638671875e-05s
INFO | --- Analysis for world-wide-web-foundation took 2.8617489337921143s
Availability | SPARQL endpoint availability check for WikiPathways took 4.1961669921875e-05s
Availability | VoID file availability check for WikiPathways took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.24847054481506348s
Reputation | Calculation of the PageRank for WikiPathways took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.9087066650390625e-05s
Believability | Calculation of trust value for WikiPathways took 6.67572021484375e-06s
INFO | --- Analysis for wp took 2.8224871158599854s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 4.172325134277344e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.2895526885986328s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 2.8133392333984375e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 7.62939453125e-06s
INFO | --- Analysis for wunderground_weatherreport took 2.829227924346924s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.1731736660003662s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0002491474151611328s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.6758527755737305s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8280000686645508s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.21912097930908203s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.5517969131469727s
Versatility | Languages check for World War 1 as Linked Open Data took 0.41069817543029785s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.21017098426818848s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.23872876167297363s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.32389307022094727s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.29429006576538086s
Availability | RDF dump link check for World War 1 as Linked Open Data took 7.749587535858154s
License | MR license check for World War 1 as Linked Open Data took 0.2712061405181885s
License | HR license check for World War 1 as Linked Open Data took 1.735412359237671s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.20542240142822266s
Understandability | Number of label check for World War 1 as Linked Open Data took 1.0440647602081299s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.35960865020751953s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.21216511726379395s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.18657875061035156s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.15848040580749512s
Performance | Throughput check for World War 1 as Linked Open Data took 11.007339477539062s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.06887984275817871s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.1648731231689453s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.2026047706604004s
Interlinking | skos check for World War 1 as Linked Open Data took 0.16417932510375977s
Interlinking | skos check for World War 1 as Linked Open Data took 0.17460060119628906s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.3349332809448242s
Currency | Creation date check for World War 1 as Linked Open Data took 0.32799720764160156s
Currency | Modification date check for World War 1 as Linked Open Data took 0.1680610179901123s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 1.9719712734222412s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 6.773449420928955s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.498291015625s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.16410088539123535s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.16496753692626953s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.1623916625976562s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.049829721450805664s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.32186031341552734s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.17281031608581543s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.5749742984771729s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.1937332153320312s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.409269094467163s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.586129903793335s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.186201810836792s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.6508941650390625s
Security | Sign check for World War 1 as Linked Open Data took 0.3038480281829834s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1526.586091041565s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 1.3408639430999756s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.02167654037475586s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 9.965896606445312e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 5.2560951709747314s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 8.821487426757812e-06s
INFO | --- Analysis for ww1lod took 1612.078385591507s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 4.172325134277344e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.2669839859008789s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.02126598358154297s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 3.218650817871094e-05s
Believability | Calculation of trust value for XlendiAmphorae took 9.298324584960938e-06s
INFO | --- Analysis for xlendiamphorae took 2.8847291469573975s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 4.1484832763671875e-05s
Availability | VoID file availability check for xLiD-Lexica took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.2505459785461426s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 6.961822509765625e-05s
Believability | Calculation of trust value for xLiD-Lexica took 9.059906005859375e-06s
INFO | --- Analysis for xlid-lexica took 2.8473780155181885s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 5.459785461425781e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.2621440887451172s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.838539123535156e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 8.344650268554688e-06s
INFO | --- Analysis for xwn took 2.8578126430511475s
Availability | SPARQL endpoint availability check for YAGO took 4.3392181396484375e-05s
Availability | VoID file availability check for YAGO took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for YAGO took 0.2702009677886963s
Reputation | Calculation of the PageRank for YAGO took 0.020942211151123047s
Interlinking | Calculation of Degree of Connection for YAGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.0001323223114013672s
Believability | Calculation of trust value for YAGO took 8.821487426757812e-06s
INFO | --- Analysis for yago took 2.8566606044769287s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 4.267692565917969e-05s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.2580299377441406s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 8.225440979003906e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 8.58306884765625e-06s
INFO | --- Analysis for yahoo_geoplanet took 2.87627911567688s
Availability | SPARQL endpoint availability check for Yale Senselab took 4.220008850097656e-05s
Availability | VoID file availability check for Yale Senselab took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.26645565032958984s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 2.8848648071289062e-05s
Believability | Calculation of trust value for Yale Senselab took 8.344650268554688e-06s
INFO | --- Analysis for yale_senselab took 2.828913688659668s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 4.00543212890625e-05s
Availability | VoID file availability check for Yovisto - academic video search took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.23894786834716797s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.842613220214844e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 8.106231689453125e-06s
INFO | --- Analysis for yovisto took 2.869783639907837s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 4.100799560546875e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.26512813568115234s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007529258728027344s
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 2.8285374641418457s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.1961669921875e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.2586345672607422s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.695487976074219e-05s
Believability | Calculation of trust value for yso-fi-allars took 8.344650268554688e-06s
INFO | --- Analysis for yso-fi-allars took 2.874833345413208s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.1484832763671875e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.25600290298461914s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.021791934967041016s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.000990152359008789s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 4.1961669921875e-05s
Believability | Calculation of trust value for yso-fi-ysa took 7.867813110351562e-06s
INFO | --- Analysis for yso-fi-ysa took 2.8648979663848877s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 5.435943603515625e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.2803807258605957s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.361701965332031e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 6.198883056640625e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 2.9316794872283936s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 4.38690185546875e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.2666316032409668s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.457069396972656e-05s
Believability | Calculation of trust value for zaragoza_turruta took 7.62939453125e-06s
INFO | --- Analysis for zaragoza_turruta took 2.8489062786102295s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.029273986816406e-05s
Availability | VoID file availability check for ZBW Labs took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.24763035774230957s
Reputation | Calculation of the PageRank for ZBW Labs took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 8.082389831542969e-05s
Believability | Calculation of trust value for ZBW Labs took 8.106231689453125e-06s
INFO | --- Analysis for zbw-labs took 2.7848730087280273s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.3215188980102539s
Availability | VoID file availability check for 20th Century Press Archives took 0.0002880096435546875s
Extra | Recovery of all triples for 20th Century Press Archives took 19.540639638900757s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7174944877624512s
Amount of data | Number of triples check for 20th Century Press Archives took 1.1190361976623535s
Interoperability | New terms check for 20th Century Press Archives took 1.6152653694152832s
Versatility | Languages check for 20th Century Press Archives took 3.1566214561462402s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.8454804420471191s
Interpretability | RDF structures check for 20th Century Press Archives took 0.16360020637512207s
Versatility | Serialization formats check for 20th Century Press Archives took 0.15030646324157715s
Availability | RDF dump link check for 20th Century Press Archives took 0.14501214027404785s
License | MR license check for 20th Century Press Archives took 0.14075303077697754s
License | HR license check for 20th Century Press Archives took 5.53572678565979s
Amount of data | Number of property check for 20th Century Press Archives took 0.15302753448486328s
Understandability | Number of label check for 20th Century Press Archives took 0.49840688705444336s
Understandability | URI regex check for 20th Century Press Archives took 0.2788217067718506s
Understandability | Vocabs check for 20th Century Press Archives took 0.172163724899292s
Verifiability | Authors check for 20th Century Press Archives took 0.16281461715698242s
Verifiability | Publishers check for 20th Century Press Archives took 0.1595296859741211s
Performance | Throughput check for 20th Century Press Archives took 10.588518142700195s
Amount of data | Check the number of entities for 20th Century Press Archives took 0.00011038780212402344s
Verifiability | Contribs. check for 20th Century Press Archives took 0.15144062042236328s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.13033843040466309s
Interlinking | skos check for 20th Century Press Archives took 0.24660491943359375s
Interlinking | skos check for 20th Century Press Archives took 0.23851275444030762s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.15103816986083984s
Currency | Creation date check for 20th Century Press Archives took 0.298703670501709s
Currency | Modification date check for 20th Century Press Archives took 0.3005242347717285s
Rep.Conc. | URIs length for 20th Century Press Archives took 16.795685052871704s
Interoperability | New vocabularies check for 20th Century Press Archives took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.15904712677001953s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.1617443561553955s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.14136099815368652s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 5.462416887283325s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8799352645874023s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.050514459609985s
Consistency | Disjoint class check for 20th Century Press Archives took 0.16323018074035645s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.3156306743621826s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.49641752243042s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.626024961471558s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.5427536964416504s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7965586185455322s
Security | Sign check for 20th Century Press Archives took 0.16538524627685547s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 984.9566402435303s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.9672832489013672s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00010514259338378906s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.430511474609375e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.1920928955078125e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1097.322214603424s
Availability | SPARQL endpoint availability check for zhishi.lemon took 0.00013875961303710938s
Availability | VoID file availability check for zhishi.lemon took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.26356005668640137s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.38690185546875e-05s
Believability | Calculation of trust value for zhishi.lemon took 8.58306884765625e-06s
INFO | --- Analysis for zhishi-lemon took 2.8402442932128906s
Availability | SPARQL endpoint availability check for Zhishi.me took 4.57763671875e-05s
Availability | VoID file availability check for Zhishi.me took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.2737431526184082s
Reputation | Calculation of the PageRank for Zhishi.me took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 6.842613220214844e-05s
Believability | Calculation of trust value for Zhishi.me took 1.3828277587890625e-05s
INFO | --- Analysis for zhishi-me took 3.3439393043518066s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.696846008300781e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.2913014888763428s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 6.031990051269531e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 8.106231689453125e-06s
INFO | --- Analysis for zitgist-musicbrainz took 2.991769552230835s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.31941819190979004s
Availability | VoID file availability check for performing-arts.ch took 0.00025391578674316406s
Extra | Recovery of all triples for performing-arts.ch took 17.257404804229736s
Performance | Total latancy measurement for performing-arts.ch took 0.6980133056640625s
Amount of data | Number of triples check for performing-arts.ch took 36.521352767944336s
Interoperability | New terms check for performing-arts.ch took 1.5454578399658203s
Versatility | Languages check for performing-arts.ch took 60.1397762298584s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.12097191810608s
Interpretability | RDF structures check for performing-arts.ch took 0.2039167881011963s
Versatility | Serialization formats check for performing-arts.ch took 0.16469335556030273s
Availability | RDF dump link check for performing-arts.ch took 0.1665658950805664s
License | MR license check for performing-arts.ch took 0.1670997142791748s
License | HR license check for performing-arts.ch took 60.123146295547485s
Amount of data | Number of property check for performing-arts.ch took 0.1825242042541504s
Understandability | Number of label check for performing-arts.ch took 2.6856157779693604s
Understandability | URI regex check for performing-arts.ch took 0.33125948905944824s
Understandability | Vocabs check for performing-arts.ch took 0.17420601844787598s
Verifiability | Authors check for performing-arts.ch took 0.1663990020751953s
Verifiability | Publishers check for performing-arts.ch took 0.16617894172668457s
Performance | Throughput check for performing-arts.ch took 10.954997062683105s
Amount of data | Check the number of entities for performing-arts.ch took 7.200241088867188e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.16042566299438477s
Interlinking | sameAs chians check for performing-arts.ch took 0.6536431312561035s
Interlinking | skos check for performing-arts.ch took 0.15726184844970703s
Interlinking | skos check for performing-arts.ch took 0.1752157211303711s
Timeliness | dataset update frequency check for performing-arts.ch took 0.16157269477844238s
Currency | Creation date check for performing-arts.ch took 0.32111573219299316s
Currency | Modification date check for performing-arts.ch took 0.32221078872680664s
Rep.Conc. | URIs length for performing-arts.ch took 21.701308012008667s
Interoperability | New vocabularies check for performing-arts.ch took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.16994237899780273s
Accuracy | Check Functional Property for performing-arts.ch took 0.1374645233154297s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.15479135513305664s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.14661955833435s
Accuracy | Check White space in annotation for performing-arts.ch took 2.5094025135040283s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.776301383972168s
Consistency | Disjoint class check for performing-arts.ch took 0.17834925651550293s
Consistency | Check Misplaced properties for performing-arts.ch took 0.367340087890625s
Consistency | Misplaced classes for performing-arts.ch took 8.438629150390625s
Consistency | Check Ontology hijacking for performing-arts.ch took 37.215845823287964s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 16574.190946102142s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.7858514785766602s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.9270243644714355s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.3160388469696045s
Security | Sign check for performing-arts.ch took 0.1724247932434082s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.2404701709747314s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 1.4555761814117432s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.021074295043945312s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 4.5299530029296875e-06s
Believability | Calculation of trust value for performing-arts.ch took 7.3909759521484375e-06s
INFO | --- Analysis for performing-arts.ch took 17407.718702554703s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.5270888805389404s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.256056547164917s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.1444091796875e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for The-AA-Thesaurus took 9.200196027755737s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.5297510623931885s
Availability | VoID file availability check for MiMoTextBase took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.24700140953063965s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.1444091796875e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.239776611328125e-05s
INFO | --- Analysis for MiMoTextBase took 5.867873430252075s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.47245121002197266s
Availability | VoID file availability check for National Library of Sweden took 0.0006711483001708984s
Extra | Recovery of all triples for National Library of Sweden took 5.768244743347168s
Performance | Total latancy measurement for National Library of Sweden took 1.0620472431182861s
Amount of data | Number of triples check for National Library of Sweden took 27.034104585647583s
Interoperability | New terms check for National Library of Sweden took 15.619397401809692s
Versatility | Languages check for National Library of Sweden took 0.2276926040649414s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.160263299942s
Interpretability | RDF structures check for National Library of Sweden took 0.22942042350769043s
Versatility | Serialization formats check for National Library of Sweden took 0.22638392448425293s
Availability | RDF dump link check for National Library of Sweden took 0.22397589683532715s
License | MR license check for National Library of Sweden took 0.2313845157623291s
License | HR license check for National Library of Sweden took 0.2239224910736084s
Amount of data | Number of property check for National Library of Sweden took 0.22384095191955566s
Understandability | Number of label check for National Library of Sweden took 0.2100381851196289s
Understandability | URI regex check for National Library of Sweden took 0.4367692470550537s
Understandability | Vocabs check for National Library of Sweden took 0.22481918334960938s
Verifiability | Authors check for National Library of Sweden took 0.2294178009033203s
Verifiability | Publishers check for National Library of Sweden took 0.20236515998840332s
Performance | Throughput check for National Library of Sweden took 10.639098644256592s
Amount of data | Check the number of entities for National Library of Sweden took 7.43865966796875e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.20458579063415527s
Interlinking | sameAs chians check for National Library of Sweden took 0.22380900382995605s
Interlinking | skos check for National Library of Sweden took 0.21538996696472168s
Interlinking | skos check for National Library of Sweden took 0.2138519287109375s
Timeliness | dataset update frequency check for National Library of Sweden took 0.20624184608459473s
Currency | Creation date check for National Library of Sweden took 0.4382054805755615s
Currency | Modification date check for National Library of Sweden took 0.4377157688140869s
Rep.Conc. | URIs length for National Library of Sweden took 81.08120608329773s
Interoperability | New vocabularies check for National Library of Sweden took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.21272969245910645s
Accuracy | Check Functional Property for National Library of Sweden took 0.22335147857666016s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.20221853256225586s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2697296142578125s
Consistency | Disjoint class check for National Library of Sweden took 0.2099463939666748s
Consistency | Check Misplaced properties for National Library of Sweden took 62.47847247123718s
Consistency | Misplaced classes for National Library of Sweden took 1.168778896331787s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.215733289718628s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.3006255626678467s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 63.06596827507019s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.2840297222137451s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.4015955924987793s
Security | Sign check for National Library of Sweden took 0.22464632987976074s
Availability | Check URIs Dereferenciability for National Library of Sweden took 16.39451789855957s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.3626089096069336s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 6.842613220214844e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0006735324859619141s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 2.2411346435546875e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library of Sweden took 7.867813110351562e-06s
INFO | --- Analysis for NLS took 1382.3864631652832s
Availability | SPARQL endpoint availability check for Japan Search took 1.9885149002075195s
Availability | VoID file availability check for Japan Search took 0.0002791881561279297s
Extra | Recovery of all triples for Japan Search took 3.5070810317993164s
Performance | Total latancy measurement for Japan Search took 3.1266562938690186s
Amount of data | Number of triples check for Japan Search took 4.836153745651245s
Interoperability | New terms check for Japan Search took 4.3234543800354s
Versatility | Languages check for Japan Search took 0.9298005104064941s
Interpretability | Number of blank nodes check for Japan Search took 10.311235427856445s
Interpretability | RDF structures check for Japan Search took 1.078596830368042s
Versatility | Serialization formats check for Japan Search took 1.0404438972473145s
Availability | RDF dump link check for Japan Search took 0.3405134677886963s
License | MR license check for Japan Search took 0.5054583549499512s
License | HR license check for Japan Search took 10.295509576797485s
Amount of data | Number of property check for Japan Search took 0.7093491554260254s
Understandability | Number of label check for Japan Search took 2.5170934200286865s
Understandability | URI regex check for Japan Search took 0.5895657539367676s
Understandability | Vocabs check for Japan Search took 0.9539690017700195s
Verifiability | Authors check for Japan Search took 0.2971346378326416s
Verifiability | Publishers check for Japan Search took 0.2819981575012207s
Performance | Throughput check for Japan Search took 11.352417230606079s
Amount of data | Check the number of entities for Japan Search took 7.557868957519531e-05s
Verifiability | Contribs. check for Japan Search took 0.2843048572540283s
Interlinking | sameAs chians check for Japan Search took 0.263599157333374s
Interlinking | skos check for Japan Search took 0.28022289276123047s
Interlinking | skos check for Japan Search took 0.28214359283447266s
Timeliness | dataset update frequency check for Japan Search took 0.3706696033477783s
Currency | Creation date check for Japan Search took 0.5871496200561523s
Currency | Modification date check for Japan Search took 0.567180871963501s
Rep.Conc. | URIs length for Japan Search took 14.563447713851929s
Interoperability | New vocabularies check for Japan Search took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.925739049911499s
Accuracy | Check Empty annotation labels for Japan Search took 1.704721450805664s
Accuracy | Check White space in annotation for Japan Search took 0.029514789581298828s
Accuracy | Check Datatype consistency for Japan Search took 0.0291290283203125s
Consistency | Disjoint class check for Japan Search took 0.2595181465148926s
Consistency | Check Misplaced properties for Japan Search took 11.50740361213684s
Consistency | Misplaced classes for Japan Search took 0.40135931968688965s
Consistency | Check Ontology hijacking for Japan Search took 3.666642665863037s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3153419494628906s
Consistency | Check Invalid usage of undefined properties for Japan Search took 12.598560810089111s
Conciseness | Check Extensional conciseness for Japan Search took 0.03793597221374512s
Conciseness | Check Intensional conciseness for Japan Search took 1.2138469219207764s
Security | Sign check for Japan Search took 0.29021596908569336s
Availability | Check URIs Dereferenciability for Japan Search took 18.549877405166626s
Completeness | Calculation of interlinking completeness for Japan Search took 0.7188398838043213s
Reputation | Calculation of the PageRank for Japan Search took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Japan Search took 2.288818359375e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.9073486328125e-06s
Believability | Calculation of trust value for Japan Search took 7.62939453125e-06s
INFO | --- Analysis for Japan-Search took 407.0240867137909s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.1943871974945068s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.7040469646453857s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.0967254638671875e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 7.867813110351562e-06s
INFO | --- Analysis for Rijksmuseum took 6.011531829833984s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.6134505271911621s
Availability | VoID file availability check for Finnish Public Libraries took 0.0006117820739746094s
Extra | Recovery of all triples for Finnish Public Libraries took 18.280797243118286s
Performance | Total latancy measurement for Finnish Public Libraries took 1.3260281085968018s
Amount of data | Number of triples check for Finnish Public Libraries took 60.219759702682495s
Interoperability | New terms check for Finnish Public Libraries took 17.6495623588562s
Versatility | Languages check for Finnish Public Libraries took 60.23655152320862s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.48995399475098s
Interpretability | RDF structures check for Finnish Public Libraries took 0.2442171573638916s
Versatility | Serialization formats check for Finnish Public Libraries took 0.24200129508972168s
Availability | RDF dump link check for Finnish Public Libraries took 0.24226927757263184s
License | MR license check for Finnish Public Libraries took 0.22569012641906738s
License | HR license check for Finnish Public Libraries took 56.05172944068909s
Amount of data | Number of property check for Finnish Public Libraries took 0.35967373847961426s
Understandability | Number of label check for Finnish Public Libraries took 16.293663024902344s
Understandability | URI regex check for Finnish Public Libraries took 0.5041468143463135s
Understandability | Vocabs check for Finnish Public Libraries took 0.24016380310058594s
Verifiability | Authors check for Finnish Public Libraries took 0.24898838996887207s
Verifiability | Publishers check for Finnish Public Libraries took 0.24569368362426758s
Performance | Throughput check for Finnish Public Libraries took 10.930095672607422s
Amount of data | Check the number of entities for Finnish Public Libraries took 8.344650268554688e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.27466487884521484s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.78765869140625s
Interlinking | skos check for Finnish Public Libraries took 0.26033568382263184s
Interlinking | skos check for Finnish Public Libraries took 0.2506570816040039s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.22166037559509277s
Currency | Creation date check for Finnish Public Libraries took 0.5527684688568115s
Currency | Modification date check for Finnish Public Libraries took 0.3514738082885742s
Rep.Conc. | URIs length for Finnish Public Libraries took 90.28209280967712s
Interoperability | New vocabularies check for Finnish Public Libraries took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.738893985748291s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 8.221238613128662s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.1716830730438232s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.340037822723389s
Consistency | Disjoint class check for Finnish Public Libraries took 0.16782712936401367s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.570658922195435s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 17.018956184387207s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.5349974632263184s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.61120676994324s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.7990565299987793s
Security | Sign check for Finnish Public Libraries took 0.4239230155944824s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.0418360233306885s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.8772199153900146s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.02174973487854004s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.9788742065429688e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 2.384185791015625e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 7.867813110351562e-06s
INFO | --- Analysis for FI-Library took 764.8094213008881s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 5.229651212692261s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.25362181663513184s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.02192831039428711s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0008959770202636719s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.2874603271484375e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 7.62939453125e-06s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 10.736548662185669s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.331665277481079s
Availability | VoID file availability check for National Library Netherlands took 0.0006554126739501953s
Extra | Recovery of all triples for National Library Netherlands took 0.6870849132537842s
Performance | Total latancy measurement for National Library Netherlands took 0.8007442951202393s
Amount of data | Number of triples check for National Library Netherlands took 0.15657663345336914s
Interoperability | New terms check for National Library Netherlands took 1.4495275020599365s
Versatility | Languages check for National Library Netherlands took 58.144590616226196s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.1507730484008789s
Interpretability | RDF structures check for National Library Netherlands took 0.1692051887512207s
Versatility | Serialization formats check for National Library Netherlands took 0.17021870613098145s
Availability | RDF dump link check for National Library Netherlands took 0.16415953636169434s
License | MR license check for National Library Netherlands took 0.1731710433959961s
License | HR license check for National Library Netherlands took 0.19400310516357422s
Amount of data | Number of property check for National Library Netherlands took 0.16275763511657715s
Understandability | Number of label check for National Library Netherlands took 0.15906786918640137s
Understandability | URI regex check for National Library Netherlands took 0.30304980278015137s
Understandability | Vocabs check for National Library Netherlands took 0.17076754570007324s
Verifiability | Authors check for National Library Netherlands took 0.15918660163879395s
Verifiability | Publishers check for National Library Netherlands took 0.1521604061126709s
Performance | Throughput check for National Library Netherlands took 11.00337266921997s
Amount of data | Check the number of entities for National Library Netherlands took 8.535385131835938e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.1648108959197998s
Interlinking | sameAs chians check for National Library Netherlands took 0.15602874755859375s
Interlinking | skos check for National Library Netherlands took 0.1434948444366455s
Interlinking | skos check for National Library Netherlands took 0.1432170867919922s
Timeliness | dataset update frequency check for National Library Netherlands took 0.1694786548614502s
Currency | Creation date check for National Library Netherlands took 0.28787803649902344s
Currency | Modification date check for National Library Netherlands took 0.326038122177124s
Rep.Conc. | URIs length for National Library Netherlands took 0.6422116756439209s
Interoperability | New vocabularies check for National Library Netherlands took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.1524646282196045s
Accuracy | Check Functional Property for National Library Netherlands took 0.1715562343597412s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.182755708694458s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.4331514835357666s
Accuracy | Check White space in annotation for National Library Netherlands took 0.027040481567382812s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.02723217010498047s
Consistency | Disjoint class check for National Library Netherlands took 0.1718740463256836s
Consistency | Check Misplaced properties for National Library Netherlands took 0.3006772994995117s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.6998205184936523s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 2.237499237060547s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.454923391342163s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.032621145248413086s
Security | Sign check for National Library Netherlands took 0.15570664405822754s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1771.7890276908875s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 1.0794486999511719s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.02140974998474121s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 6.818771362304688e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.4080276489257812e-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 7.3909759521484375e-06s
INFO | --- Analysis for National-Library-Netherlands took 1881.8449878692627s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.457883596420288s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007767677307128906s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.25712108612060547s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.02826690673828125s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 3.8623809814453125e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0016369819641113281s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5974044799804688e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 7.62939453125e-06s
INFO | --- Analysis for Antique-Renaissance took 6.3405375480651855s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.148370981216431s
Availability | VoID file availability check for ARTSDATA.CA took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.25697946548461914s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.0212404727935791s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0011322498321533203s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.3828277587890625e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 9.775161743164062e-06s
INFO | --- Analysis for ARTSDATA-CA took 9.327422857284546s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.17208003997802734s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.2907748222351074s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.02118682861328125s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.2159347534179688e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 1.1205673217773438e-05s
INFO | --- Analysis for ArCo took 3.392648935317993s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.260761022567749s
Availability | VoID file availability check for ConfermentSampo took 0.0002639293670654297s
Extra | Recovery of all triples for ConfermentSampo took 19.195504426956177s
Performance | Total latancy measurement for ConfermentSampo took 0.8535799980163574s
Amount of data | Number of triples check for ConfermentSampo took 7.558580636978149s
Interoperability | New terms check for ConfermentSampo took 2.5750787258148193s
Versatility | Languages check for ConfermentSampo took 25.626807928085327s
Interpretability | Number of blank nodes check for ConfermentSampo took 7.3880226612091064s
Security | Check HTTPS for ConfermentSampo took 0.4168586730957031s
Interpretability | RDF structures check for ConfermentSampo took 0.19474530220031738s
Versatility | Serialization formats check for ConfermentSampo took 0.18264460563659668s
Availability | RDF dump link check for ConfermentSampo took 3.1894426345825195s
License | MR license check for ConfermentSampo took 0.17372608184814453s
License | HR license check for ConfermentSampo took 0.24675989151000977s
Amount of data | Number of property check for ConfermentSampo took 0.1742086410522461s
Understandability | Number of label check for ConfermentSampo took 4.953122615814209s
Understandability | URI regex check for ConfermentSampo took 0.35126447677612305s
Understandability | Vocabs check for ConfermentSampo took 0.18510890007019043s
Verifiability | Authors check for ConfermentSampo took 0.16572880744934082s
Verifiability | Publishers check for ConfermentSampo took 0.16519570350646973s
Performance | Throughput check for ConfermentSampo took 10.760532140731812s
Amount of data | Check the number of entities for ConfermentSampo took 4.038500785827637s
Verifiability | Contribs. check for ConfermentSampo took 0.1701211929321289s
Interlinking | sameAs chians check for ConfermentSampo took 0.4015519618988037s
Interlinking | skos check for ConfermentSampo took 0.17214107513427734s
Interlinking | skos check for ConfermentSampo took 0.16884469985961914s
Timeliness | dataset update frequency check for ConfermentSampo took 0.18489909172058105s
Currency | Creation date check for ConfermentSampo took 0.3360762596130371s
Currency | Modification date check for ConfermentSampo took 0.32801008224487305s
Rep.Conc. | URIs length for ConfermentSampo took 34.12446856498718s
Interoperability | New vocabularies check for ConfermentSampo took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.1722710132598877s
Accuracy | Check Functional Property for ConfermentSampo took 0.1667780876159668s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.16795945167541504s
Accuracy | Check Empty annotation labels for ConfermentSampo took 14.483801126480103s
Accuracy | Check White space in annotation for ConfermentSampo took 3.017688035964966s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.1465513706207275s
Consistency | Disjoint class check for ConfermentSampo took 0.17457294464111328s
Consistency | Check Misplaced properties for ConfermentSampo took 6.374818801879883s
Consistency | Check Ontology hijacking for ConfermentSampo took 14.03732442855835s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.4710206985473633s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.5956881046295166s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.835002899169922s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.17859530448913574s
Security | Sign check for ConfermentSampo took 0.1835346221923828s
Availability | Check URIs Dereferenciability for ConfermentSampo took 2.477932929992676s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.3311138153076172s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.02082085609436035s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 2.288818359375e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0006804466247558594s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.33514404296875e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 1.9073486328125e-06s
Believability | Calculation of trust value for ConfermentSampo took 7.3909759521484375e-06s
INFO | --- Analysis for ConfermentSampo took 310.7649486064911s
Availability | SPARQL endpoint availability check for Museum Finland took 0.23414850234985352s
Availability | VoID file availability check for Museum Finland took 0.00026297569274902344s
Extra | Recovery of all triples for Museum Finland took 7.619784355163574s
Performance | Total latancy measurement for Museum Finland took 0.8371729850769043s
Amount of data | Number of triples check for Museum Finland took 0.32201576232910156s
Interoperability | New terms check for Museum Finland took 1.883606195449829s
Versatility | Languages check for Museum Finland took 0.6638205051422119s
Interpretability | Number of blank nodes check for Museum Finland took 0.3309023380279541s
Security | Check HTTPS for Museum Finland took 0.2611410617828369s
Interpretability | RDF structures check for Museum Finland took 0.2884712219238281s
Versatility | Serialization formats check for Museum Finland took 0.1858372688293457s
Availability | RDF dump link check for Museum Finland took 0.165374755859375s
License | MR license check for Museum Finland took 0.2302238941192627s
License | HR license check for Museum Finland took 0.4240696430206299s
Amount of data | Number of property check for Museum Finland took 0.1563720703125s
Understandability | Number of label check for Museum Finland took 0.4560999870300293s
Understandability | URI regex check for Museum Finland took 0.34287405014038086s
Understandability | Vocabs check for Museum Finland took 0.16995477676391602s
Verifiability | Authors check for Museum Finland took 0.1732313632965088s
Verifiability | Publishers check for Museum Finland took 0.17380404472351074s
Performance | Throughput check for Museum Finland took 11.121555805206299s
Amount of data | Check the number of entities for Museum Finland took 0.00011801719665527344s
Verifiability | Contribs. check for Museum Finland took 0.1595444679260254s
Interlinking | sameAs chians check for Museum Finland took 0.19898748397827148s
Interlinking | skos check for Museum Finland took 0.15951132774353027s
Interlinking | skos check for Museum Finland took 0.16684532165527344s
Timeliness | dataset update frequency check for Museum Finland took 0.17767834663391113s
Currency | Creation date check for Museum Finland took 0.33991527557373047s
Currency | Modification date check for Museum Finland took 0.34928441047668457s
Rep.Conc. | URIs length for Museum Finland took 3.545954465866089s
Interoperability | New vocabularies check for Museum Finland took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.1657395362854004s
Accuracy | Check Functional Property for Museum Finland took 0.1785902976989746s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.16246557235717773s
Accuracy | Check Empty annotation labels for Museum Finland took 1.006683588027954s
Accuracy | Check White space in annotation for Museum Finland took 0.06172800064086914s
Accuracy | Check Datatype consistency for Museum Finland took 0.9840664863586426s
Consistency | Disjoint class check for Museum Finland took 0.15750622749328613s
Consistency | Check Misplaced properties for Museum Finland took 0.616506814956665s
Consistency | Check Ontology hijacking for Museum Finland took 2.897200584411621s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.624572515487671s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.8418307304382324s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6885912418365479s
Conciseness | Check Intensional conciseness for Museum Finland took 0.24065089225769043s
Security | Sign check for Museum Finland took 0.15768885612487793s
Availability | Check URIs Dereferenciability for Museum Finland took 8.511128664016724s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.2704172134399414s
Reputation | Calculation of the PageRank for Museum Finland took 0.021979331970214844s
Interlinking | Calculation of Degree of Connection for Museum Finland took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0010387897491455078s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.86102294921875e-06s
Believability | Calculation of trust value for Museum Finland took 8.344650268554688e-06s
INFO | --- Analysis for FI-Museum took 67.08047533035278s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.1653456687927246s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0007030963897705078s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.514830827713013s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.7923076152801514s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 32.181145906448364s
Interoperability | New terms check for Mapping Manuscript Migrations took 5.0206921100616455s
Versatility | Languages check for Mapping Manuscript Migrations took 75.73459196090698s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 30.18695068359375s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.24922490119934082s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.1582963466644287s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.16727256774902344s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.1721034049987793s
License | MR license check for Mapping Manuscript Migrations took 0.17048311233520508s
License | HR license check for Mapping Manuscript Migrations took 1.7818408012390137s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.1701827049255371s
Understandability | Number of label check for Mapping Manuscript Migrations took 9.082955837249756s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.33472728729248047s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.1754148006439209s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.17176270484924316s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.17419743537902832s
Performance | Throughput check for Mapping Manuscript Migrations took 11.302648305892944s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0638494491577148s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.1698625087738037s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.4934976100921631s
Interlinking | skos check for Mapping Manuscript Migrations took 0.15857529640197754s
Interlinking | skos check for Mapping Manuscript Migrations took 0.1675097942352295s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.17021536827087402s
Currency | Creation date check for Mapping Manuscript Migrations took 0.3744237422943115s
Currency | Modification date check for Mapping Manuscript Migrations took 0.17089200019836426s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 49.001214027404785s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.17023539543151855s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.17115259170532227s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.1627509593963623s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.576547861099243s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.4091389179229736s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.696505784988403s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.17058777809143066s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 23.762704610824585s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 15.897879362106323s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.5845296382904053s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 3.0204741954803467s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 4.28478217124939s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.1746354103088379s
Security | Sign check for Mapping Manuscript Migrations took 0.1620335578918457s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1544.6108763217926s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 1.385610818862915s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.02128887176513672s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0008616447448730469s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 2.2172927856445312e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 3.0994415283203125e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.33514404296875e-05s
INFO | --- Analysis for MMM took 1959.3577539920807s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.17904162406921387s
Availability | VoID file availability check for Semantic Kalevala took 0.000324249267578125s
Extra | Recovery of all triples for Semantic Kalevala took 8.181371927261353s
Performance | Total latancy measurement for Semantic Kalevala took 0.8234372138977051s
Amount of data | Number of triples check for Semantic Kalevala took 0.46030545234680176s
Interoperability | New terms check for Semantic Kalevala took 2.35992431640625s
Versatility | Languages check for Semantic Kalevala took 0.9073269367218018s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.36719202995300293s
Security | Check HTTPS for Semantic Kalevala took 0.42421436309814453s
Interpretability | RDF structures check for Semantic Kalevala took 0.24025464057922363s
Versatility | Serialization formats check for Semantic Kalevala took 0.1671609878540039s
Availability | RDF dump link check for Semantic Kalevala took 0.1744370460510254s
License | MR license check for Semantic Kalevala took 0.20838570594787598s
License | HR license check for Semantic Kalevala took 1.2109136581420898s
Amount of data | Number of property check for Semantic Kalevala took 0.1582796573638916s
Understandability | Number of label check for Semantic Kalevala took 0.5202038288116455s
Understandability | URI regex check for Semantic Kalevala took 0.3430309295654297s
Understandability | Vocabs check for Semantic Kalevala took 0.1747267246246338s
Verifiability | Authors check for Semantic Kalevala took 0.19195342063903809s
Verifiability | Publishers check for Semantic Kalevala took 0.16919398307800293s
Performance | Throughput check for Semantic Kalevala took 10.954625368118286s
Amount of data | Check the number of entities for Semantic Kalevala took 7.033348083496094e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.19110107421875s
Interlinking | sameAs chians check for Semantic Kalevala took 0.17972040176391602s
Interlinking | skos check for Semantic Kalevala took 0.25266051292419434s
Interlinking | skos check for Semantic Kalevala took 0.17487525939941406s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.1867375373840332s
Currency | Creation date check for Semantic Kalevala took 0.34813356399536133s
Currency | Modification date check for Semantic Kalevala took 0.33785128593444824s
Rep.Conc. | URIs length for Semantic Kalevala took 5.126840353012085s
Interoperability | New vocabularies check for Semantic Kalevala took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.26935672760009766s
Accuracy | Check Functional Property for Semantic Kalevala took 0.17023897171020508s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.17454767227172852s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 2.1275386810302734s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.29188108444213867s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.39493727684021s
Consistency | Disjoint class check for Semantic Kalevala took 0.17155194282531738s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7498986721038818s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.3534233570098877s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.4448883533477783s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.6485075950622559s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.915306568145752s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.17890620231628418s
Security | Sign check for Semantic Kalevala took 0.17739272117614746s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2721.4403076171875s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 1.9469404220581055s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.020678997039794922s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.1920928955078125e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.9073486328125e-06s
Believability | Calculation of trust value for Semantic Kalevala took 7.62939453125e-06s
INFO | --- Analysis for Semantic-Kalevala took 2789.988153219223s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.8874619007110596s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.00035572052001953125s
Extra | Recovery of all triples for Smithsonian American Art Museum took 288.3320252895355s
Performance | Total latancy measurement for Smithsonian American Art Museum took 2.9400858879089355s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5806596279144287s
Interoperability | New terms check for Smithsonian American Art Museum took 3.2574853897094727s
Versatility | Languages check for Smithsonian American Art Museum took 27.482232093811035s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.7239227294921875s
Security | Check HTTPS for Smithsonian American Art Museum took 0.440110445022583s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.7773897647857666s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.7918055057525635s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.7105245590209961s
License | MR license check for Smithsonian American Art Museum took 0.7228350639343262s
License | HR license check for Smithsonian American Art Museum took 17.835165977478027s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5747942924499512s
Understandability | Number of label check for Smithsonian American Art Museum took 0.6516132354736328s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1966240406036377s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.6013545989990234s
Verifiability | Authors check for Smithsonian American Art Museum took 0.576592206954956s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5949230194091797s
Performance | Throughput check for Smithsonian American Art Museum took 11.813783645629883s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.557868957519531e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.5790822505950928s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5887134075164795s
Interlinking | skos check for Smithsonian American Art Museum took 0.5719394683837891s
Interlinking | skos check for Smithsonian American Art Museum took 0.5870368480682373s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5934302806854248s
Currency | Creation date check for Smithsonian American Art Museum took 1.1804699897766113s
Currency | Modification date check for Smithsonian American Art Museum took 1.2310290336608887s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 108.29400587081909s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.2159347534179688e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5993866920471191s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 21.56485676765442s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.49579381942749023s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.243483304977417s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5901415348052979s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 5.2559192180633545s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 97.98592329025269s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.6805384159088135s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.983494281768799s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9266011714935303s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6399557590484619s
Security | Sign check for Smithsonian American Art Museum took 0.6158409118652344s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.234401226043701s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 1.3395636081695557s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.021430253982543945s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.811981201171875e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 5.7220458984375e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 8.58306884765625e-06s
INFO | --- Analysis for Smithsonian took 718.0449175834656s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.16022896766662598s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.2570030689239502s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.021213769912719727s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.3113021850585938e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 7.867813110351562e-06s
INFO | --- Analysis for Zeri-Photo-Archive took 15.466600179672241s
Availability | SPARQL endpoint availability check for Archives Hub took 21.40584373474121s
Availability | VoID file availability check for Archives Hub took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.262113094329834s
Reputation | Calculation of the PageRank for Archives Hub took 0.022441387176513672s
Interlinking | Calculation of Degree of Connection for Archives Hub took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.1920928955078125e-05s
Believability | Calculation of trust value for Archives Hub took 7.867813110351562e-06s
INFO | --- Analysis for Archives-Hub took 54.84997582435608s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.3704702854156494s
Availability | VoID file availability check for Yale centre of British Art took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.2558741569519043s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.021409273147583008s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.239776611328125e-05s
Believability | Calculation of trust value for Yale centre of British Art took 7.867813110351562e-06s
INFO | --- Analysis for Yale took 4.266808032989502s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 261.9644310474396s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.2643473148345947s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.3589859008789062e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 7.152557373046875e-06s
INFO | --- Analysis for ADL took 536.8993644714355s
Availability | SPARQL endpoint availability check for MusicKG took 0.7192296981811523s
Availability | VoID file availability check for MusicKG took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for MusicKG took 0.2573976516723633s
Reputation | Calculation of the PageRank for MusicKG took 0.020996809005737305s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for MusicKG took 2.2411346435546875e-05s
Believability | Calculation of trust value for MusicKG took 8.344650268554688e-06s
INFO | --- Analysis for MusicKG took 5.757546424865723s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.988459587097168s
Availability | VoID file availability check for CIDOC-CRM took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.23956656455993652s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.02081131935119629s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.2159347534179688e-05s
Believability | Calculation of trust value for CIDOC-CRM took 7.62939453125e-06s
INFO | --- Analysis for CIDOC-CRM took 4.506299257278442s
Availability | SPARQL endpoint availability check for Mondis took 0.3755941390991211s
Availability | VoID file availability check for Mondis took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Mondis took 0.23767352104187012s
Reputation | Calculation of the PageRank for Mondis took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for Mondis took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.2636184692382812e-05s
Believability | Calculation of trust value for Mondis took 8.344650268554688e-06s
INFO | --- Analysis for Mondis took 3.6858904361724854s
Availability | SPARQL endpoint availability check for DigitalNZ took 2.791391134262085s
Availability | VoID file availability check for DigitalNZ took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.748100996017456s
Reputation | Calculation of the PageRank for DigitalNZ took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.2159347534179688e-05s
Believability | Calculation of trust value for DigitalNZ took 7.62939453125e-06s
INFO | --- Analysis for DigitalNZ took 6.989162445068359s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.17621302604675293s
Availability | VoID file availability check for Fondazione Zeri took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.26757287979125977s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.4543533325195312e-05s
Believability | Calculation of trust value for Fondazione Zeri took 6.4373016357421875e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.1080944538116455s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.2782721519470215s
Availability | VoID file availability check for Digital Public Library of America took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.27609944343566895s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.021294593811035156s
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.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.2159347534179688e-05s
Believability | Calculation of trust value for Digital Public Library of America took 7.62939453125e-06s
INFO | --- Analysis for Library-of-America took 4.1200878620147705s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.530390977859497s
Availability | VoID file availability check for Auckland Museum took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.26326894760131836s
Reputation | Calculation of the PageRank for Auckland Museum took 0.020585298538208008s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.239776611328125e-05s
Believability | Calculation of trust value for Auckland Museum took 7.152557373046875e-06s
INFO | --- Analysis for Auckland-Museum took 6.086548805236816s
Availability | SPARQL endpoint availability check for National Library of Spain took 3.2596914768218994s
Availability | VoID file availability check for National Library of Spain took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.2829892635345459s
Reputation | Calculation of the PageRank for National Library of Spain took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.1205673217773438e-05s
Believability | Calculation of trust value for National Library of Spain took 7.62939453125e-06s
INFO | --- Analysis for BNE took 6.157674074172974s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.512911081314087s
Availability | VoID file availability check for National Library of Korea took 0.00030875205993652344s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.24394893646240234s
Reputation | Calculation of the PageRank for National Library of Korea took 0.021396398544311523s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.2636184692382812e-05s
Believability | Calculation of trust value for National Library of Korea took 7.867813110351562e-06s
INFO | --- Analysis for Korea-Library took 5.416494607925415s
Availability | SPARQL endpoint availability check for The State Russian Museum took 2.192578077316284s
Availability | VoID file availability check for The State Russian Museum took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.2582261562347412s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.1682510375976562e-05s
Believability | Calculation of trust value for The State Russian Museum took 8.106231689453125e-06s
INFO | --- Analysis for Russian-Museum took 5.005266189575195s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.7455790042877197s
Availability | VoID file availability check for National Library of Scotland took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.2478640079498291s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.2874603271484375e-05s
Believability | Calculation of trust value for National Library of Scotland took 7.152557373046875e-06s
INFO | --- Analysis for National-Library-of-Scotland took 7.043966293334961s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.338564395904541s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.24157071113586426s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.2159347534179688e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 7.62939453125e-06s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.3259568214416504s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.2004995346069336s
Availability | VoID file availability check for OntoComedySources took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.2561910152435303s
Reputation | Calculation of the PageRank for OntoComedySources took 0.021228790283203125s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.2159347534179688e-05s
Believability | Calculation of trust value for OntoComedySources took 7.152557373046875e-06s
INFO | --- Analysis for OntoComedySources took 3.7216291427612305s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.20415496826171875s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.27666401863098145s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.2874603271484375e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 7.867813110351562e-06s
INFO | --- Analysis for OntoCeramic-2.0 took 4.421045541763306s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.1821913719177246s
Availability | VoID file availability check for SaintGall Ontology took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.2494034767150879s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.021422863006591797s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.3113021850585938e-05s
Believability | Calculation of trust value for SaintGall Ontology took 8.106231689453125e-06s
INFO | --- Analysis for SaintGall-Ontology took 3.004049777984619s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.9216275215148926s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.2603724002838135s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.2874603271484375e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 7.62939453125e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 4.103256464004517s
Availability | SPARQL endpoint availability check for ICON took 0.3599724769592285s
Availability | VoID file availability check for ICON took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for ICON took 0.2580118179321289s
Reputation | Calculation of the PageRank for ICON took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for ICON took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for ICON took 1.239776611328125e-05s
Believability | Calculation of trust value for ICON took 7.3909759521484375e-06s
INFO | --- Analysis for ICON took 4.098764657974243s
Availability | SPARQL endpoint availability check for Polifonia took 0.24591660499572754s
Availability | VoID file availability check for Polifonia took 0.0009016990661621094s
Completeness | Calculation of interlinking completeness for Polifonia took 0.27968788146972656s
Reputation | Calculation of the PageRank for Polifonia took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.1920928955078125e-05s
Believability | Calculation of trust value for Polifonia took 8.106231689453125e-06s
INFO | --- Analysis for Polifonia took 4.329949855804443s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.24643182754516602s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0003075599670410156s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.24578332901000977s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.021071195602416992s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.0967254638671875e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 7.152557373046875e-06s
INFO | --- Analysis for Atlas-of-Paths took 3.870433807373047s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.1893470287322998s
Availability | VoID file availability check for Music Note Ontology took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.25119686126708984s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.2159347534179688e-05s
Believability | Calculation of trust value for Music Note Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for Music-Note-Ontology took 7.6698009967803955s
Availability | SPARQL endpoint availability check for HaMSE took 0.21198487281799316s
Availability | VoID file availability check for HaMSE took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for HaMSE took 0.266132116317749s
Reputation | Calculation of the PageRank for HaMSE took 0.020787954330444336s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.0728836059570312e-05s
Believability | Calculation of trust value for HaMSE took 9.298324584960938e-06s
INFO | --- Analysis for HaMSE took 4.520497798919678s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.08057951927185059s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.24354147911071777s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.1682510375976562e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 7.62939453125e-06s
INFO | --- Analysis for FOod took 4.6870832443237305s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.6921143531799316s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.24863052368164062s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.239776611328125e-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.872631311416626s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 0.5225658416748047s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0007660388946533203s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.26640820503234863s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.1444091796875e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 8.58306884765625e-06s
INFO | --- Analysis for ARIADNE took 4.172088861465454s
Availability | SPARQL endpoint availability check for Nomisma.org  took 1.2889738082885742s
Availability | VoID file availability check for Nomisma.org  took 0.0002620220184326172s
Extra | Recovery of all triples for Nomisma.org  took 300.1031029224396s
Performance | Total latancy measurement for Nomisma.org  took 2.1562609672546387s
Amount of data | Number of triples check for Nomisma.org  took 40.354467153549194s
Interoperability | New terms check for Nomisma.org  took 12.36446213722229s
Versatility | Languages check for Nomisma.org  took 95.28769111633301s
Interpretability | Number of blank nodes check for Nomisma.org  took 33.15796661376953s
Security | Check HTTPS for Nomisma.org  took 1.0622856616973877s
Interpretability | RDF structures check for Nomisma.org  took 0.48494505882263184s
Versatility | Serialization formats check for Nomisma.org  took 0.42719006538391113s
Availability | RDF dump link check for Nomisma.org  took 978.3145287036896s
License | MR license check for Nomisma.org  took 0.47397351264953613s
License | HR license check for Nomisma.org  took 63.58042621612549s
Amount of data | Number of property check for Nomisma.org  took 0.47016429901123047s
Understandability | Number of label check for Nomisma.org  took 7.37000584602356s
Understandability | URI regex check for Nomisma.org  took 0.8384387493133545s
Understandability | Vocabs check for Nomisma.org  took 0.410266637802124s
Verifiability | Authors check for Nomisma.org  took 0.4674391746520996s
Verifiability | Publishers check for Nomisma.org  took 0.5835232734680176s
Performance | Throughput check for Nomisma.org  took 13.770087480545044s
Amount of data | Check the number of entities for Nomisma.org  took 0.0003437995910644531s
Verifiability | Contribs. check for Nomisma.org  took 0.5864295959472656s
Interlinking | sameAs chians check for Nomisma.org  took 0.4282674789428711s
Interlinking | skos check for Nomisma.org  took 1.36444091796875s
Interlinking | skos check for Nomisma.org  took 0.6093795299530029s
Timeliness | dataset update frequency check for Nomisma.org  took 0.4319760799407959s
Currency | Creation date check for Nomisma.org  took 0.862055778503418s
Currency | Modification date check for Nomisma.org  took 0.43064141273498535s
Rep.Conc. | URIs length for Nomisma.org  took 695.5363438129425s
Interoperability | New vocabularies check for Nomisma.org  took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.48222994804382324s
Accuracy | Check Functional Property for Nomisma.org  took 0.46363401412963867s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.4433250427246094s
Accuracy | Check Empty annotation labels for Nomisma.org  took 621.4562387466431s
Accuracy | Check White space in annotation for Nomisma.org  took 2.757254123687744s
Consistency | Disjoint class check for Nomisma.org  took 0.45482611656188965s
Consistency | Check Misplaced properties for Nomisma.org  took 25.933931827545166s
Consistency | Check Ontology hijacking for Nomisma.org  took 600.3811841011047s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 26.761516332626343s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.00013875961303710938s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.4474802017211914s
Security | Sign check for Nomisma.org  took 0.6046817302703857s
Availability | Check URIs Dereferenciability for Nomisma.org  took 2475.3659460544586s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.1707005500793457s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.021158933639526367s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 7.152557373046875e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.9073486328125e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.0967254638671875e-05s
INFO | --- Analysis for nomisma_org took 9466.961488723755s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.863739013671875e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.6863901615142822s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.918212890625e-05s
Believability | Calculation of trust value for Discogs in RDF took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-discogs took 7.392255544662476s
Availability | SPARQL endpoint availability check for Enslaved.org took 7.796287536621094e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.27694106101989746s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.0279159545898438e-05s
Believability | Calculation of trust value for Enslaved.org took 7.3909759521484375e-06s
INFO | --- Analysis for enslaved.org took 3.721595287322998s
Availability | SPARQL endpoint availability check for EventKG took 4.410743713378906e-05s
Availability | VoID file availability check for EventKG took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for EventKG took 0.2764871120452881s
Reputation | Calculation of the PageRank for EventKG took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.416175842285156e-05s
Believability | Calculation of trust value for EventKG took 8.106231689453125e-06s
INFO | --- Analysis for eventkg took 4.483035326004028s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.22890043258666992s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006756782531738281s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 29.64075231552124s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.4364888668060303s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.789402961730957s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.6024971008300781s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 4.997941255569458s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.411025047302246s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.08763766288757324s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.08733010292053223s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.07710719108581543s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.08533239364624023s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.09351372718811035s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.09125399589538574s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.08654332160949707s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.15629196166992188s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.08356404304504395s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.086090087890625s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.09358501434326172s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.271256923675537s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 5.9604644775390625e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.08489727973937988s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.08446478843688965s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.09206962585449219s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08507013320922852s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.07824158668518066s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.17766261100769043s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.17938613891601562s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 19.1921226978302s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 1.33514404296875e-05s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.09473967552185059s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.09119725227355957s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.08362174034118652s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.9609005451202393s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.07800674438476562s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 3.0478017330169678s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 6.39889669418335s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.4873967170715332s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.405178070068359s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.0860462188720703s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.08401679992675781s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 500.69985699653625s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 1.2473711967468262s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.021172523498535156s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 2.384185791015625e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 9.059906005859375e-06s
INFO | --- Analysis for roceeh-road took 616.5891699790955s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.20178818702697754s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006623268127441406s
Extra | Recovery of all triples for Thesaurus BNCF took 47.56444334983826s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5391342639923096s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6234133243560791s
Interoperability | New terms check for Thesaurus BNCF took 1.4164412021636963s
Versatility | Languages check for Thesaurus BNCF took 6.652490854263306s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8929905891418457s
Security | Check HTTPS for Thesaurus BNCF took 0.07654023170471191s
Interpretability | RDF structures check for Thesaurus BNCF took 0.09405732154846191s
Versatility | Serialization formats check for Thesaurus BNCF took 0.09591031074523926s
Availability | RDF dump link check for Thesaurus BNCF took 0.08467531204223633s
License | MR license check for Thesaurus BNCF took 0.08509230613708496s
License | HR license check for Thesaurus BNCF took 0.17548680305480957s
Amount of data | Number of property check for Thesaurus BNCF took 0.09579348564147949s
Understandability | Number of label check for Thesaurus BNCF took 0.24609088897705078s
Understandability | URI regex check for Thesaurus BNCF took 0.17520904541015625s
Understandability | Vocabs check for Thesaurus BNCF took 0.09937167167663574s
Verifiability | Authors check for Thesaurus BNCF took 0.09239315986633301s
Verifiability | Publishers check for Thesaurus BNCF took 0.09684348106384277s
Performance | Throughput check for Thesaurus BNCF took 10.712607622146606s
Amount of data | Check the number of entities for Thesaurus BNCF took 9.608268737792969e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.10301446914672852s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.09114956855773926s
Interlinking | skos check for Thesaurus BNCF took 0.15346455574035645s
Interlinking | skos check for Thesaurus BNCF took 0.14346694946289062s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.09638404846191406s
Currency | Creation date check for Thesaurus BNCF took 0.1868607997894287s
Currency | Modification date check for Thesaurus BNCF took 0.18869709968566895s
Rep.Conc. | URIs length for Thesaurus BNCF took 29.07246685028076s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.09424781799316406s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.09410929679870605s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.1450517177581787s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 14.75350570678711s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4952571392059326s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.06758451461792s
Consistency | Disjoint class check for Thesaurus BNCF took 0.09559011459350586s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8280518054962158s
Consistency | Misplaced classes for Thesaurus BNCF took 6.920310735702515s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 10.062068700790405s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.608276128768921s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.453625440597534s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.5489394664764404s
Security | Sign check for Thesaurus BNCF took 0.08952474594116211s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 22.39707088470459s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.7364275455474854s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02077317237854004s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.05718994140625e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.1457672119140625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.049041748046875e-05s
INFO | --- Analysis for bncf-ns took 190.21962213516235s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.095414161682129s
Availability | VoID file availability check for COURAGE Dataset took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.26007938385009766s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.0517578125e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.5735626220703125e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 4.671882629394531s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.839897155761719e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2609364986419678s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.021226882934570312s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.552436828613281e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.001071929931640625s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.5299530029296875e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for bll-thesaurus took 3.277676582336426s
Availability | SPARQL endpoint availability check for Inztrow took 4.291534423828125e-05s
Availability | VoID file availability check for Inztrow took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2724192142486572s
Reputation | Calculation of the PageRank for Inztrow took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for Inztrow took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Inztrow took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.8371810913085938e-05s
Believability | Calculation of trust value for Inztrow took 7.867813110351562e-06s
INFO | --- Analysis for Inztrow took 2.922093152999878s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 2.2147207260131836s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.25170159339904785s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0008614063262939453s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.982948303222656e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 5.341192722320557s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.2438507080078125e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2461850643157959s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 2.86102294921875e-05s
Believability | Calculation of trust value for Temples of the Classical World took 6.67572021484375e-06s
INFO | --- Analysis for classical_temples took 3.287315607070923s
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.5586748123168945s
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.00023603439331054688s
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.2555851936340332s
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.020442962646484375s
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 9.5367431640625e-06s
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.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.343292236328125e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 6.433958053588867s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.143390655517578s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.25287866592407227s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.58306884765625e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 4.936731815338135s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.153564691543579s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.28452110290527344s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02086639404296875s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.029273986816406e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-CRB took 4.976072788238525s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.141512632369995s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.26160693168640137s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020990610122680664s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.845329284667969e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 6.198883056640625e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 5.014241695404053s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.1365816593170166s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2473444938659668s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-DQOT took 4.930261611938477s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.1316211223602295s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2620699405670166s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020671844482421875s
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.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.939338684082031e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 4.950970649719238s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.0811781883239746s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0003795623779296875s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.27367544174194336s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020939350128173828s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.891654968261719e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.3828277587890625e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 5.913940906524658s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.1306347846984863s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.25011754035949707s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020768404006958008s
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.239776611328125e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.745887756347656e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.4836273193359375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 5.021195411682129s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.124783992767334s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.26764369010925293s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.02086949348449707s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.054473876953125e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0967254638671875e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 4.953272342681885s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.448837995529175s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2597770690917969s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.7206878662109375e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 6.312711954116821s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.139216184616089s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2684009075164795s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02097320556640625s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.653236389160156e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 5.089983701705933s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 2.11826753616333s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.23640847206115723s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020828962326049805s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.392333984375e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 5.9604644775390625e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 4.91148042678833s
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.1295011043548584s
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.0002484321594238281s
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.24835896492004395s
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.020797014236450195s
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.1205673217773438e-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.0007448196411132812s
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.130073547363281e-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 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 4.927523851394653s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.1310861110687256s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.29242897033691406s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.57763671875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC_-_DNB took 5.126439332962036s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.47693490982055664s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0002472400665283203s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.7068750858306885s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.3776524066925049s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.37825608253479004s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.940770149230957s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 42.00924515724182s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.2951362133026123s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.16319489479064941s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.4119863510131836s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.28852224349975586s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.28702354431152344s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.3672311305999756s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 20.526665210723877s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3239595890045166s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.5956392288208008s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.5621504783630371s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.29531407356262207s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.3487052917480469s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.34692835807800293s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.303094148635864s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 0.00011086463928222656s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.2934703826904297s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.30126261711120605s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3414933681488037s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.27155637741088867s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.2847626209259033s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.58296799659729s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5869555473327637s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.2377922534942627s
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.2845332622528076s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4074225425720215s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4118039608001709s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.5481722354888916s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03319406509399414s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.02838754653930664s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.3312811851501465s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.418823480606079s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.34463977813720703s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.9005095958709717s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2672014236450195s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.443897008895874s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.032146453857421875s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.2774677276611328s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.28830623626708984s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1491.1928520202637s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.9494059085845947s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02129197120666504s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 8.344650268554688e-06s
INFO | --- Analysis for BVMC took 1626.6502401828766s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.9132673740387s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.3230459690093994s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.021070241928100586s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.6716461181640625e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 9.5367431640625e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 668.9077851772308s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.7454543113708496s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.7145962715148926s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.021682262420654297s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LucaniPharsalia took 6.1884613037109375s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.4588124752044678s
Availability | VoID file availability check for Querolus in LiLa took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.2724292278289795s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.02114129066467285s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Querolus in LiLa took 8.344650268554688e-06s
INFO | --- Analysis for Querolus took 5.131922960281372s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.5273287296295166s
Availability | VoID file availability check for UDante in LiLa took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.2638278007507324s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.021751880645751953s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0008649826049804688s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 4.291534423828125e-05s
Believability | Calculation of trust value for UDante in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for UDante took 3.866084098815918s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.46072936058044434s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002789497375488281s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.1628122329711914s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.8225562572479248s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3306427001953125s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.7125437259674072s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.13098907470703s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18964242935180664s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4202103614807129s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1735692024230957s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15776491165161133s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23481392860412598s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3383643627166748s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14793825149536133s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26754283905029297s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.33141016960144043s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1553056240081787s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19223237037658691s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20134496688842773s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.739302635192871s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.081031799316406e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.295076847076416s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.44219398498535156s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 1.0193216800689697s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1373128890991211s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17779922485351562s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5982887744903564s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4975106716156006s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.0684354305267334s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16704893112182617s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.30135679244995117s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.30402684211730957s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6009328365325928s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028291702270507812s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02828049659729004s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.46227431297302246s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2059741020202637s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9551334381103516s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.300776720046997s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5042972564697266s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03315162658691406s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.20912957191467285s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15543413162231445s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2406.9307022094727s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.5945215225219727s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020183324813842773s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0006744861602783203s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.458427429199219e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.2159347534179688e-05s
INFO | --- Analysis for ceo took 2536.4165666103363s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.46218109130859375s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.00026154518127441406s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 78.05645489692688s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.401679515838623s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6430685520172119s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.2432234287261963s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.7490460872650146s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5938975811004639s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.2834479808807373s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.27945828437805176s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 13.317098140716553s
License | MR license check for Cultural Heritage Thesaurus took 0.2896914482116699s
License | HR license check for Cultural Heritage Thesaurus took 0.34644269943237305s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.26932644844055176s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3060152530670166s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5786161422729492s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.2753322124481201s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.29177308082580566s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.2946813106536865s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.342590808868408s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.058547973632812e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2627091407775879s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.26743602752685547s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.27245044708251953s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.30490779876708984s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.2942240238189697s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5690114498138428s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.548823356628418s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 28.420180559158325s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.8714075088500977s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.30422186851501465s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.3220100402832031s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.28249239921569824s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 6.296490907669067s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22113513946533203s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.27107930183410645s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.1622378826141357s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.25872254371643066s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.046322822570801s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.2119462490081787s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00016927719116210938s
Security | Sign check for Cultural Heritage Thesaurus took 0.29523587226867676s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 250.97089958190918s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 1.3251664638519287s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.022185325622558594s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 2.8133392333984375e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00014328956604003906s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.49634861946105957s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for cht took 440.0510196685791s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.9889869689941406s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.26520681381225586s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.0221707820892334s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0008745193481445312s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.893013000488281e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.0013580322265625e-05s
INFO | --- Analysis for greekchildrensartmuseum took 5.129063129425049s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.8160552978515625e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.7028937339782715s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020884275436401367s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.772445678710938e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.9141387939453125e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 3.7622036933898926s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.320019721984863s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.26870036125183105s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02118539810180664s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0008835792541503906s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 6.628036499023438e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 6.67572021484375e-06s
INFO | --- Analysis for ldt@library took 15.64790964126587s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7018923759460449s
Availability | VoID file availability check for Muziekweb took 0.00025343894958496094s
Extra | Recovery of all triples for Muziekweb took 1.4304335117340088s
Performance | Total latancy measurement for Muziekweb took 1.5529065132141113s
Amount of data | Number of triples check for Muziekweb took 0.3806781768798828s
Interoperability | New terms check for Muziekweb took 1.6942293643951416s
Versatility | Languages check for Muziekweb took 43.452953577041626s
Interpretability | Number of blank nodes check for Muziekweb took 0.3070545196533203s
Interpretability | RDF structures check for Muziekweb took 0.44930505752563477s
Versatility | Serialization formats check for Muziekweb took 0.30152273178100586s
Availability | RDF dump link check for Muziekweb took 0.31661391258239746s
License | MR license check for Muziekweb took 0.3008089065551758s
License | HR license check for Muziekweb took 11.452064514160156s
Amount of data | Number of property check for Muziekweb took 0.3018474578857422s
Understandability | Number of label check for Muziekweb took 0.6172149181365967s
Understandability | URI regex check for Muziekweb took 0.6500680446624756s
Understandability | Vocabs check for Muziekweb took 0.30622005462646484s
Verifiability | Authors check for Muziekweb took 0.32257866859436035s
Verifiability | Publishers check for Muziekweb took 0.3397064208984375s
Performance | Throughput check for Muziekweb took 12.23146390914917s
Amount of data | Check the number of entities for Muziekweb took 4.00543212890625e-05s
Verifiability | Contribs. check for Muziekweb took 0.3112757205963135s
Interlinking | sameAs chians check for Muziekweb took 0.31178712844848633s
Interlinking | skos check for Muziekweb took 0.3055989742279053s
Interlinking | skos check for Muziekweb took 0.27892303466796875s
Timeliness | dataset update frequency check for Muziekweb took 0.3097848892211914s
Currency | Creation date check for Muziekweb took 0.7697386741638184s
Currency | Modification date check for Muziekweb took 0.7533993721008301s
Rep.Conc. | URIs length for Muziekweb took 1.818976640701294s
Interoperability | New vocabularies check for Muziekweb took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.3314690589904785s
Accuracy | Check Functional Property for Muziekweb took 0.4649770259857178s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.48496222496032715s
Accuracy | Check Empty annotation labels for Muziekweb took 0.8844201564788818s
Accuracy | Check White space in annotation for Muziekweb took 0.027451276779174805s
Accuracy | Check Datatype consistency for Muziekweb took 0.02791738510131836s
Consistency | Disjoint class check for Muziekweb took 0.36783647537231445s
Consistency | Check Misplaced properties for Muziekweb took 1.146723747253418s
Consistency | Check Ontology hijacking for Muziekweb took 2.0733213424682617s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.2773301601409912s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.5938856601715088s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03218889236450195s
Conciseness | Check Intensional conciseness for Muziekweb took 0.32729053497314453s
Security | Sign check for Muziekweb took 0.36445188522338867s
Availability | Check URIs Dereferenciability for Muziekweb took 1869.292469739914s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.955559492111206s
Reputation | Calculation of the PageRank for Muziekweb took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for Muziekweb took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.1920928955078125e-06s
Believability | Calculation of trust value for Muziekweb took 7.152557373046875e-06s
INFO | --- Analysis for muziekweb took 1984.1504034996033s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 5.476809740066528s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.2703080177307129s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020739316940307617s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.131431579589844e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.0728836059570312e-05s
INFO | --- Analysis for nom took 11.284598588943481s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 9.429944515228271s
Availability | VoID file availability check for Linked Stage Graph took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.2766263484954834s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 4.935264587402344e-05s
Believability | Calculation of trust value for Linked Stage Graph took 6.4373016357421875e-06s
INFO | --- Analysis for slod took 18.942555904388428s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 0.22046709060668945s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0002655982971191406s
Extra | Recovery of all triples for WASABI RDF Knowledge Graph took 2.574723958969116s
Performance | Total latancy measurement for WASABI RDF Knowledge Graph took 0.35319089889526367s
Amount of data | Number of triples check for WASABI RDF Knowledge Graph took 72.15478754043579s
Interoperability | New terms check for WASABI RDF Knowledge Graph took 2.2017815113067627s
Versatility | Languages check for WASABI RDF Knowledge Graph took 300.0612804889679s
Interpretability | Number of blank nodes check for WASABI RDF Knowledge Graph took 81.72003293037415s
Interpretability | RDF structures check for WASABI RDF Knowledge Graph took 0.1175079345703125s
Versatility | Serialization formats check for WASABI RDF Knowledge Graph took 0.12655210494995117s
Availability | RDF dump link check for WASABI RDF Knowledge Graph took 10.354846477508545s
License | MR license check for WASABI RDF Knowledge Graph took 0.1828911304473877s
License | HR license check for WASABI RDF Knowledge Graph took 300.05444860458374s
Amount of data | Number of property check for WASABI RDF Knowledge Graph took 0.1219794750213623s
Understandability | Number of label check for WASABI RDF Knowledge Graph took 3.700784683227539s
Understandability | URI regex check for WASABI RDF Knowledge Graph took 0.3371598720550537s
Understandability | Vocabs check for WASABI RDF Knowledge Graph took 0.07983088493347168s
Verifiability | Authors check for WASABI RDF Knowledge Graph took 0.07462954521179199s
Verifiability | Publishers check for WASABI RDF Knowledge Graph took 0.07859468460083008s
Performance | Throughput check for WASABI RDF Knowledge Graph took 10.327275037765503s
Amount of data | Check the number of entities for WASABI RDF Knowledge Graph took 0.10413527488708496s
Verifiability | Contribs. check for WASABI RDF Knowledge Graph took 0.212249755859375s
Interlinking | sameAs chians check for WASABI RDF Knowledge Graph took 0.08689999580383301s
Interlinking | skos check for WASABI RDF Knowledge Graph took 0.08177876472473145s
Interlinking | skos check for WASABI RDF Knowledge Graph took 0.07681488990783691s
Timeliness | dataset update frequency check for WASABI RDF Knowledge Graph took 0.39449429512023926s
Currency | Creation date check for WASABI RDF Knowledge Graph took 0.1594839096069336s
Currency | Modification date check for WASABI RDF Knowledge Graph took 0.1594681739807129s
Rep.Conc. | URIs length for WASABI RDF Knowledge Graph took 38.13689947128296s
Interoperability | New vocabularies check for WASABI RDF Knowledge Graph took 10.210954904556274s
Consistency | Deprecated classes/propertiers check for WASABI RDF Knowledge Graph took 0.07800650596618652s
Accuracy | Check Functional Property for WASABI RDF Knowledge Graph took 0.29014039039611816s
Accuracy | Check Inverse Functional Property for WASABI RDF Knowledge Graph took 0.289886474609375s
Accuracy | Check Empty annotation labels for WASABI RDF Knowledge Graph took 1.1592159271240234s
Accuracy | Check White space in annotation for WASABI RDF Knowledge Graph took 0.08307600021362305s
Accuracy | Check Datatype consistency for WASABI RDF Knowledge Graph took 0.07890105247497559s
Consistency | Disjoint class check for WASABI RDF Knowledge Graph took 0.0883488655090332s
Consistency | Check Misplaced properties for WASABI RDF Knowledge Graph took 47.47139024734497s
Consistency | Misplaced classes for WASABI RDF Knowledge Graph took 1.321350336074829s
Consistency | Check Ontology hijacking for WASABI RDF Knowledge Graph took 2.491490364074707s
Consistency | Check Invalid usage of undefined classes for WASABI RDF Knowledge Graph took 1.3453459739685059s
Consistency | Check Invalid usage of undefined properties for WASABI RDF Knowledge Graph took 30.41293978691101s
Conciseness | Check Extensional conciseness for WASABI RDF Knowledge Graph took 0.08415675163269043s
Conciseness | Check Intensional conciseness for WASABI RDF Knowledge Graph took 1.22407865524292s
Security | Sign check for WASABI RDF Knowledge Graph took 0.4694373607635498s
Availability | Check URIs Dereferenciability for WASABI RDF Knowledge Graph took 20.193923711776733s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 1.4610636234283447s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02122330665588379s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 8.988380432128906e-05s
Interoperability | Check the re-using of existing vocabs for WASABI RDF Knowledge Graph took 11.312058925628662s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.2159347534179688e-05s
INFO | --- Analysis for wasabi took 13288.337180376053s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2356700897216797s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0003116130828857422s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.26524996757507324s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.02171182632446289s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 2.9802322387695312e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for wl-kg took 4.832997798919678s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.2586522102355957s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.020221471786499023s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.364418029785156e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 1.1444091796875e-05s
INFO | --- Analysis for yso took 3.3188188076019287s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.315376281738281e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.29001903533935547s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020378589630126953s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.7894973754882812e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 6.67572021484375e-06s
INFO | --- Analysis for ISSN:0080-3626 took 3.2984731197357178s
Availability | SPARQL endpoint availability check for Copyright Free Music took 5.078315734863281e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0004143714904785156s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.2641315460205078s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.910064697265625e-05s
Believability | Calculation of trust value for Copyright Free Music took 9.5367431640625e-06s
INFO | --- Analysis for Copyright_Free_Music took 2.883915424346924s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 5.125999450683594e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.26522397994995117s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.02045607566833496s
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.0008177757263183594s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.8848648071289062e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 6.4373016357421875e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.8746397495269775s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.3392181396484375e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.2641258239746094s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 2.8133392333984375e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 7.3909759521484375e-06s
INFO | --- Analysis for Sherry_Wine took 2.8391106128692627s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.410743713378906e-05s
Availability | VoID file availability check for Sherry Wine took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.2633321285247803s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.8371810913085938e-05s
Believability | Calculation of trust value for Sherry Wine took 7.62939453125e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.7977867126464844s
Availability | SPARQL endpoint availability check for Freeyork took 7.557868957519531e-05s
Availability | VoID file availability check for Freeyork took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2502906322479248s
Reputation | Calculation of the PageRank for Freeyork took 0.021259784698486328s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0009329319000244141s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00013637542724609375s
Believability | Calculation of trust value for Freeyork took 6.9141387939453125e-06s
INFO | --- Analysis for freeyork-org took 2.858574628829956s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.2438507080078125e-05s
Availability | VoID file availability check for Informatics Studies took 0.0003502368927001953s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.25755739212036133s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020846843719482422s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007088184356689453s
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 2.8822104930877686s
Availability | SPARQL endpoint availability check for MappingChange took 0.3538391590118408s
Availability | VoID file availability check for MappingChange took 0.0002720355987548828s
Extra | Recovery of all triples for MappingChange took 68.50240707397461s
Performance | Total latancy measurement for MappingChange took 1.4167709350585938s
Amount of data | Number of triples check for MappingChange took 17.639860153198242s
Interoperability | New terms check for MappingChange took 4.430401563644409s
Versatility | Languages check for MappingChange took 41.8091139793396s
Interpretability | Number of blank nodes check for MappingChange took 14.902591705322266s
Interpretability | RDF structures check for MappingChange took 0.2846512794494629s
Versatility | Serialization formats check for MappingChange took 0.2886393070220947s
Availability | RDF dump link check for MappingChange took 0.28886938095092773s
License | MR license check for MappingChange took 0.28551387786865234s
License | HR license check for MappingChange took 5.353108167648315s
Amount of data | Number of property check for MappingChange took 0.2816650867462158s
Understandability | Number of label check for MappingChange took 2.237229585647583s
Understandability | URI regex check for MappingChange took 0.5767092704772949s
Understandability | Vocabs check for MappingChange took 0.2811918258666992s
Verifiability | Authors check for MappingChange took 0.28902173042297363s
Verifiability | Publishers check for MappingChange took 0.28601646423339844s
Performance | Throughput check for MappingChange took 11.418170928955078s
Amount of data | Check the number of entities for MappingChange took 6.008148193359375e-05s
Verifiability | Contribs. check for MappingChange took 0.29044151306152344s
Interlinking | sameAs chians check for MappingChange took 0.29046130180358887s
Interlinking | skos check for MappingChange took 0.2838759422302246s
Interlinking | skos check for MappingChange took 0.2835390567779541s
Timeliness | dataset update frequency check for MappingChange took 0.2923886775970459s
Currency | Creation date check for MappingChange took 0.5665483474731445s
Currency | Modification date check for MappingChange took 0.5678234100341797s
Rep.Conc. | URIs length for MappingChange took 55.8301215171814s
Interoperability | New vocabularies check for MappingChange took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for MappingChange took 0.29450416564941406s
Accuracy | Check Functional Property for MappingChange took 0.28255462646484375s
Accuracy | Check Inverse Functional Property for MappingChange took 0.28335070610046387s
Accuracy | Check Empty annotation labels for MappingChange took 4.672144174575806s
Accuracy | Check White space in annotation for MappingChange took 0.4522116184234619s
Accuracy | Check Datatype consistency for MappingChange took 4.8925371170043945s
Consistency | Disjoint class check for MappingChange took 0.2772798538208008s
Consistency | Check Misplaced properties for MappingChange took 9.69806456565857s
Consistency | Check Ontology hijacking for MappingChange took 33.57359790802002s
Consistency | Check Invalid usage of undefined classes for MappingChange took 1.485818862915039s
Consistency | Check Invalid usage of undefined properties for MappingChange took 11.064223766326904s
Conciseness | Check Extensional conciseness for MappingChange took 3.08455491065979s
Conciseness | Check Intensional conciseness for MappingChange took 0.3374910354614258s
Security | Sign check for MappingChange took 0.2820594310760498s
Availability | Check URIs Dereferenciability for MappingChange took 2091.493441581726s
Completeness | Calculation of interlinking completeness for MappingChange took 0.5891444683074951s
Reputation | Calculation of the PageRank for MappingChange took 0.021195650100708008s
Interlinking | Calculation of Degree of Connection for MappingChange took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for MappingChange took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for MappingChange took 1.6450881958007812e-05s
Interoperability | Check the re-using of existing vocabs for MappingChange took 1.9073486328125e-06s
Believability | Calculation of trust value for MappingChange took 7.62939453125e-06s
INFO | --- Analysis for mappingch took 2480.448032617569s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.30386972427368164s
Availability | VoID file availability check for Odeuropa Ontology took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.27071523666381836s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.1205673217773438e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for Odeuropa took 4.070211410522461s

--- Total time for analysis:75489.01765465736s ---
--- Total time for analysis:20.96917157073816 hours ---