Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.696846008300781e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.6932990550994873s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.5381975173950195s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0008790493011474609s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00042128562927246094s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 8.344650268554688e-06s
INFO | --- Analysis for 0080-3626 took 8.097170114517212s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.553794860839844e-05s
Availability | VoID file availability check for 土地利用图 took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.706923246383667s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.170967102050781e-05s
Believability | Calculation of trust value for 土地利用图 took 7.867813110351562e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 3.1905674934387207s
Availability | SPARQL endpoint availability check for 113322 took 4.458427429199219e-05s
Availability | VoID file availability check for 113322 took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for 113322 took 0.2828829288482666s
Reputation | Calculation of the PageRank for 113322 took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for 113322 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 113322 took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.075599670410156e-05s
Believability | Calculation of trust value for 113322 took 9.059906005859375e-06s
INFO | --- Analysis for 11 took 4.680368900299072s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.4345855712890625e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2489619255065918s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 2.9325485229492188e-05s
Believability | Calculation of trust value for Korepetycje Buki took 8.58306884765625e-06s
INFO | --- Analysis for 12323 took 2.359877109527588s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06463432312011719s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.24840044975280762s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.58306884765625e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 8.106231689453125e-06s
INFO | --- Analysis for 2000-us-census-rdf took 2.377593994140625s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.8318531513214111s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.27126574516296387s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.814697265625e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 5.7220458984375e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 5.9856908321380615s
Availability | SPARQL endpoint availability check for Open Data Web took 0.26608943939208984s
Availability | VoID file availability check for Open Data Web took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2839338779449463s
Reputation | Calculation of the PageRank for Open Data Web took 0.020305395126342773s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.3855438232421875e-05s
Believability | Calculation of trust value for Open Data Web took 9.059906005859375e-06s
INFO | --- Analysis for _data.odw.tw took 2.703176498413086s
Availability | SPARQL endpoint availability check for 土地利用 took 5.3882598876953125e-05s
Availability | VoID file availability check for 土地利用 took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2880070209503174s
Reputation | Calculation of the PageRank for 土地利用 took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.170967102050781e-05s
Believability | Calculation of trust value for 土地利用 took 7.867813110351562e-06s
INFO | --- Analysis for _data1.odw.tw took 2.4022884368896484s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.482269287109375e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0007646083831787109s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2542233467102051s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020252227783203125s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.123283386230469e-05s
Believability | Calculation of trust value for 土地利用模型 took 7.152557373046875e-06s
INFO | --- Analysis for _data2.odw.tw took 5.434797763824463s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.054473876953125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0003714561462402344s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2606055736541748s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8371810913085938e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.3909759521484375e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.7665364742279053s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.267692565917969e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2836191654205322s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.647804260253906e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 7.3909759521484375e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 27.380402088165283s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 5.1975250244140625e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.280040979385376s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.86102294921875e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 4.76837158203125e-06s
INFO | --- Analysis for A1 took 2.8800275325775146s
Availability | SPARQL endpoint availability check for SummerOlympics took 1.9842257499694824s
Availability | VoID file availability check for SummerOlympics took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.26392126083374023s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.4849853515625e-05s
Believability | Calculation of trust value for SummerOlympics took 7.152557373046875e-06s
INFO | --- Analysis for abc took 6.462174415588379s
Availability | SPARQL endpoint availability check for Test_m took 4.291534423828125e-05s
Availability | VoID file availability check for Test_m took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Test_m took 0.26292967796325684s
Reputation | Calculation of the PageRank for Test_m took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for Test_m took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.0040740966796875e-05s
Believability | Calculation of trust value for Test_m took 1.2874603271484375e-05s
INFO | --- Analysis for ABC took 2.368330240249634s
Availability | SPARQL endpoint availability check for my intro took 4.363059997558594e-05s
Availability | VoID file availability check for my intro took 0.000244140625s
Completeness | Calculation of interlinking completeness for my intro took 0.2595548629760742s
Reputation | Calculation of the PageRank for my intro took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for my intro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for my intro took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for my intro took 2.9087066650390625e-05s
Believability | Calculation of trust value for my intro took 7.152557373046875e-06s
INFO | --- Analysis for abhay_intro took 2.3052637577056885s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.4433107376098633s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.26486992835998535s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020328521728515625s
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.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.000102996826171875s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for abs-linked-data took 2.872314214706421s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 5.984306335449219e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.26180219650268555s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.02090287208557129s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0010104179382324219s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.910064697265625e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 8.106231689453125e-06s
INFO | --- Analysis for academic-offer-of-unl took 2.8720381259918213s
Availability | SPARQL endpoint availability check for AcadOnto took 4.839897155761719e-05s
Availability | VoID file availability check for AcadOnto took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.2611210346221924s
Reputation | Calculation of the PageRank for AcadOnto took 0.02098989486694336s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0010142326354980469s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.814697265625e-05s
Believability | Calculation of trust value for AcadOnto took 7.867813110351562e-06s
INFO | --- Analysis for acadonto took 4.305051326751709s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.090819358825684s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2689943313598633s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.695487976074219e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.245208740234375e-06s
INFO | --- Analysis for acorn-sat took 35.21621012687683s
Availability | SPARQL endpoint availability check for Addgene took 4.267692565917969e-05s
Availability | VoID file availability check for Addgene took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for Addgene took 0.2717859745025635s
Reputation | Calculation of the PageRank for Addgene took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for Addgene took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.409385681152344e-05s
Believability | Calculation of trust value for Addgene took 1.0967254638671875e-05s
INFO | --- Analysis for addgene took 15.866697788238525s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.410743713378906e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2664926052093506s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020192384719848633s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.1552734375e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 7.152557373046875e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 5.219068288803101s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.6105940341949463s
Availability | VoID file availability check for AEMET metereological dataset took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.25118565559387207s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.62396240234375e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 8.106231689453125e-06s
INFO | --- Analysis for aemet took 4.860158681869507s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.315376281738281e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.28136491775512695s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.075599670410156e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 8.344650268554688e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.9344849586486816s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.032472848892211914s
Availability | VoID file availability check for AgriNepalData took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.26950597763061523s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.081031799316406e-05s
Believability | Calculation of trust value for AgriNepalData took 9.5367431640625e-06s
INFO | --- Analysis for agrinepaldata took 2.495739221572876s
Availability | SPARQL endpoint availability check for AGRIS took 262.1404232978821s
Availability | VoID file availability check for AGRIS took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for AGRIS took 0.31939101219177246s
Reputation | Calculation of the PageRank for AGRIS took 0.02065277099609375s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.724761962890625e-05s
Believability | Calculation of trust value for AGRIS took 8.106231689453125e-06s
INFO | --- Analysis for agris took 555.2388634681702s
Availability | SPARQL endpoint availability check for AGROVOC took 0.22310352325439453s
Availability | VoID file availability check for AGROVOC took 0.0005745887756347656s
Extra | Recovery of all triples for AGROVOC took 30.864232778549194s
Performance | Total latancy measurement for AGROVOC took 0.4412686824798584s
Amount of data | Number of triples check for AGROVOC took 30.072916269302368s
Interoperability | New terms check for AGROVOC took 3.2839319705963135s
Versatility | Languages check for AGROVOC took 30.07141089439392s
Interpretability | Number of blank nodes check for AGROVOC took 30.081472635269165s
Interpretability | RDF structures check for AGROVOC took 0.09259343147277832s
Versatility | Serialization formats check for AGROVOC took 0.09266376495361328s
Availability | RDF dump link check for AGROVOC took 0.08985495567321777s
License | MR license check for AGROVOC took 0.09624600410461426s
License | HR license check for AGROVOC took 0.8329813480377197s
Amount of data | Number of property check for AGROVOC took 0.10558271408081055s
Understandability | Number of label check for AGROVOC took 30.097477197647095s
Understandability | URI regex check for AGROVOC took 0.1691758632659912s
Understandability | Vocabs check for AGROVOC took 0.09031796455383301s
Verifiability | Authors check for AGROVOC took 0.08712053298950195s
Verifiability | Publishers check for AGROVOC took 0.08883094787597656s
Performance | Throughput check for AGROVOC took 10.468183755874634s
Amount of data | Check the number of entities for AGROVOC took 7.271766662597656e-05s
Verifiability | Contribs. check for AGROVOC took 0.07806777954101562s
Interlinking | sameAs chians check for AGROVOC took 0.08873939514160156s
Interlinking | skos check for AGROVOC took 6.5223541259765625s
Interlinking | skos check for AGROVOC took 5.478247880935669s
Timeliness | dataset update frequency check for AGROVOC took 0.14862775802612305s
Currency | Creation date check for AGROVOC took 0.21646571159362793s
Currency | Modification date check for AGROVOC took 0.18172574043273926s
Rep.Conc. | URIs length for AGROVOC took 46.63354015350342s
Interoperability | New vocabularies check for AGROVOC took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.08734345436096191s
Accuracy | Check Empty annotation labels for AGROVOC took 28.340038776397705s
Accuracy | Check White space in annotation for AGROVOC took 2.9963769912719727s
Consistency | Disjoint class check for AGROVOC took 0.08897662162780762s
Consistency | Check Misplaced properties for AGROVOC took 18.082369327545166s
Consistency | Check Ontology hijacking for AGROVOC took 30.179028272628784s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 21.218509435653687s
Conciseness | Check Extensional conciseness for AGROVOC took 0.00015354156494140625s
Conciseness | Check Intensional conciseness for AGROVOC took 0.0869452953338623s
Security | Sign check for AGROVOC took 0.09697890281677246s
Completeness | Calculation of interlinking completeness for AGROVOC took 1.2960894107818604s
Reputation | Calculation of the PageRank for AGROVOC took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011134147644042969s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 2.1457672119140625e-06s
Believability | Calculation of trust value for AGROVOC took 8.344650268554688e-06s
INFO | --- Analysis for agrovoc took 409.3307514190674s
Availability | SPARQL endpoint availability check for AGROVOC took 4.38690185546875e-05s
Availability | VoID file availability check for AGROVOC took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.7021825313568115s
Reputation | Calculation of the PageRank for AGROVOC took 0.02036595344543457s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.793571472167969e-05s
Believability | Calculation of trust value for AGROVOC took 7.867813110351562e-06s
INFO | --- Analysis for agrovoc-skos took 4.140116453170776s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.5111958980560303s
Availability | VoID file availability check for Analytics India Magazine took 0.00037097930908203125s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.24769210815429688s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.02012181282043457s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 2.8371810913085938e-05s
Believability | Calculation of trust value for Analytics India Magazine took 7.62939453125e-06s
INFO | --- Analysis for AIM took 5.241889476776123s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.744529724121094e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.253709077835083s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020192384719848633s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 2.956390380859375e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 7.152557373046875e-06s
INFO | --- Analysis for AISHE took 2.3036293983459473s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.410743713378906e-05s
Availability | VoID file availability check for  equipment ontology took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.24880337715148926s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for  equipment ontology took 7.62939453125e-06s
INFO | --- Analysis for akash took 2.323211908340454s
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.0002772808074951172s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.25507044792175293s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 2.9087066650390625e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 7.62939453125e-06s
INFO | --- Analysis for aksworg took 2.826017141342163s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.363059997558594e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.25233960151672363s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0008952617645263672s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.528594970703125e-05s
Believability | Calculation of trust value for AlchemyAPI took 8.58306884765625e-06s
INFO | --- Analysis for alchemyapi took 2.860490083694458s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.38690185546875e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.23805856704711914s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.02022409439086914s
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.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.9802322387695312e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 7.3909759521484375e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.822269916534424s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.305495262145996s
Availability | VoID file availability check for aliada-scanbit-net took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.26732540130615234s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02035689353942871s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.0001125335693359375s
Believability | Calculation of trust value for aliada-scanbit-net took 7.867813110351562e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.2020955085754395s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.1484832763671875e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.256960391998291s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.9325485229492188e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 7.62939453125e-06s
INFO | --- Analysis for allen-brain-atlas took 2.8267621994018555s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 1.4205539226531982s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006306171417236328s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 552.1415629386902s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.708085775375366s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.5128755569458008s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.6639413833618164s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.07908487319946s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 4.054794788360596s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8974144458770752s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.5875024795532227s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.653144121170044s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5586056709289551s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5856738090515137s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 33.01923131942749s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.613013505935669s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.792823076248169s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1170873641967773s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5621600151062012s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6276650428771973s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5678064823150635s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.756971836090088s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 3.981590270996094e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5405311584472656s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.566096305847168s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5885980129241943s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5559713840484619s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.565598726272583s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.1350908279418945s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.109623670578003s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 191.7278139591217s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 25.592400789260864s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.577221155166626s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.5939137935638428s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.5670206546783447s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 146.0917043685913s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.038577079772949s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.6196353435516357s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6019432544708252s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 11.034075498580933s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.740098714828491s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 129.75757122039795s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3667161464691162s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.932398319244385s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7402873039245605s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8416101932525635s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5822513103485107s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12917.831629514694s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.1152653694152832s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02203679084777832s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0008034706115722656s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 9.036064147949219e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 2.7825233936309814s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 8.106231689453125e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 14453.027044296265s
Availability | SPARQL endpoint availability check for Alojamientos took 4.2438507080078125e-05s
Availability | VoID file availability check for Alojamientos took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.2603626251220703s
Reputation | Calculation of the PageRank for Alojamientos took 0.021419525146484375s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0011205673217773438s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.886222839355469e-05s
Believability | Calculation of trust value for Alojamientos took 7.62939453125e-06s
INFO | --- Analysis for alojamientos-zaragoza took 3.864365816116333s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.299882173538208s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.7090656757354736s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.6716461181640625e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 2.0742416381835938e-05s
INFO | --- Analysis for alpino-rdf took 4.4916322231292725s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.410743713378906e-05s
Availability | VoID file availability check for AAT-atawil took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.25749874114990234s
Reputation | Calculation of the PageRank for AAT-atawil took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.075599670410156e-05s
Believability | Calculation of trust value for AAT-atawil took 7.62939453125e-06s
INFO | --- Analysis for Altawil took 2.4182302951812744s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.744529724121094e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00034046173095703125s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.2632136344909668s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.0279159545898438e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 8.344650268554688e-06s
INFO | --- Analysis for am-collections-online took 3.5756893157958984s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.935264587402344e-05s
Availability | VoID file availability check for Amer Nejma took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.2671024799346924s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 2.956390380859375e-05s
Believability | Calculation of trust value for Amer Nejma took 7.62939453125e-06s
INFO | --- Analysis for Amer_Nejma took 2.2763259410858154s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.27526235580444336s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 7.62939453125e-06s
INFO | --- Analysis for amon took 2.924293041229248s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.736290454864502s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.2449934482574463s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 8.869171142578125e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 7.867813110351562e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.7399539947509766s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 7.462501525878906e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.255129337310791s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.0279159545898438e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 1.0967254638671875e-05s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 3.2869818210601807s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.458427429199219e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.2577223777770996s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.790855407714844e-05s
Believability | Calculation of trust value for Animal Diversity Web took 7.867813110351562e-06s
INFO | --- Analysis for animal-diversity-web took 2.814405679702759s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.4345855712890625e-05s
Availability | VoID file availability check for Anime Dataset took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.2652292251586914s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Anime Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for Anime took 4.107494592666626s
Availability | SPARQL endpoint availability check for ANNO took 4.482269287109375e-05s
Availability | VoID file availability check for ANNO took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for ANNO took 0.27860569953918457s
Reputation | Calculation of the PageRank for ANNO took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.218650817871094e-05s
Believability | Calculation of trust value for ANNO took 8.106231689453125e-06s
INFO | --- Analysis for anno took 4.2218263149261475s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.506111145019531e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.001050710678100586s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.27744269371032715s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.653236389160156e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 7.152557373046875e-06s
INFO | --- Analysis for AntiqueCarsCollection took 2.7896461486816406s
Availability | SPARQL endpoint availability check for apache took 4.482269287109375e-05s
Availability | VoID file availability check for apache took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for apache took 0.2829151153564453s
Reputation | Calculation of the PageRank for apache took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for apache took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for apache took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for apache took 5.5789947509765625e-05s
Believability | Calculation of trust value for apache took 7.867813110351562e-06s
INFO | --- Analysis for apache took 3.1754631996154785s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.28348422050476074s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 6.008148193359375e-05s
Believability | Calculation of trust value for Apertium RDF took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf took 4.931711673736572s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2560436725616455s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.9596850872039795s
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.0006358623504638672s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.2605435848236084s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.1961669921875e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.6382715702056885s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.25331974029541016s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020915746688842773s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 6.866455078125e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.629366874694824s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.24783635139465332s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.579692363739014s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0003533363342285156s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.25653600692749023s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.599578619003296s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.696846008300781e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.26044607162475586s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.664840936660767s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 7.414817810058594e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2879066467285156s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.771714925765991s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2619493007659912s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.630059719085693s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.792213439941406e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2643313407897949s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020711898803710938s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 8.821487426757812e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.576828241348267s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006964206695556641s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2661612033843994s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0008218288421630859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.56566309928894s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 6.198883056640625e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.2504856586456299s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.887580871582031e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 24.979983806610107s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.24605441093444824s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 5.735919713973999s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 9.417533874511719e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.26041555404663086s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 3.170967102050781e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 5.643373489379883s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2631816864013672s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0010120868682861328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 5.125999450683594e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 5.508138179779053s
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.0007066726684570312s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.24999499320983887s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.1961669921875e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.462444543838501s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.28166937828063965s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.533966541290283s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.00012564659118652344s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.27294015884399414s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.557193040847778s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.26970338821411133s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.395159006118774s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2523665428161621s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.59439754486084s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2764139175415039s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.1961669921875e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.549588918685913s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2662694454193115s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.5357019901275635s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2604050636291504s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 5.9604644775390625e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.748107194900513s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.8012046813964844s
Availability | VoID file availability check for AragoDBPedia took 0.0007276535034179688s
Extra | Recovery of all triples for AragoDBPedia took 3.1732404232025146s
Performance | Total latancy measurement for AragoDBPedia took 1.9737610816955566s
Amount of data | Number of triples check for AragoDBPedia took 0.976534366607666s
Interoperability | New terms check for AragoDBPedia took 2.264207124710083s
Versatility | Languages check for AragoDBPedia took 60.5114541053772s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.868367433547974s
Security | Check HTTPS for AragoDBPedia took 0.2643435001373291s
Interpretability | RDF structures check for AragoDBPedia took 0.970820426940918s
Versatility | Serialization formats check for AragoDBPedia took 1.9513120651245117s
Availability | RDF dump link check for AragoDBPedia took 0.40532350540161133s
License | MR license check for AragoDBPedia took 0.7849588394165039s
License | HR license check for AragoDBPedia took 7.454694747924805s
Amount of data | Number of property check for AragoDBPedia took 0.40213727951049805s
Understandability | Number of label check for AragoDBPedia took 0.7166004180908203s
Understandability | URI regex check for AragoDBPedia took 0.9895956516265869s
Understandability | Vocabs check for AragoDBPedia took 0.44246864318847656s
Verifiability | Authors check for AragoDBPedia took 0.5495748519897461s
Verifiability | Publishers check for AragoDBPedia took 0.44080471992492676s
Performance | Throughput check for AragoDBPedia took 11.664015531539917s
Amount of data | Check the number of entities for AragoDBPedia took 7.271766662597656e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.5271263122558594s
Interlinking | sameAs chians check for AragoDBPedia took 0.4491744041442871s
Interlinking | skos check for AragoDBPedia took 0.68338942527771s
Interlinking | skos check for AragoDBPedia took 0.41556739807128906s
Timeliness | dataset update frequency check for AragoDBPedia took 1.0743064880371094s
Currency | Creation date check for AragoDBPedia took 2.1675548553466797s
Currency | Modification date check for AragoDBPedia took 0.889927864074707s
Rep.Conc. | URIs length for AragoDBPedia took 6.922354221343994s
Interoperability | New vocabularies check for AragoDBPedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.4035224914550781s
Accuracy | Check Functional Property for AragoDBPedia took 0.47548413276672363s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.5433475971221924s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.345271348953247s
Accuracy | Check White space in annotation for AragoDBPedia took 0.030439138412475586s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.027130842208862305s
Consistency | Disjoint class check for AragoDBPedia took 0.4081244468688965s
Consistency | Check Misplaced properties for AragoDBPedia took 4.675550937652588s
Consistency | Misplaced classes for AragoDBPedia took 0.7396650314331055s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.814592123031616s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3588447570800781s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.559959888458252s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03158426284790039s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.6241872310638428s
Security | Sign check for AragoDBPedia took 0.7480947971343994s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3307.567132949829s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.1656007766723633s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.02156829833984375s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0008742809295654297s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 5.125999450683594e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBPedia took 5.4836273193359375e-06s
INFO | --- Analysis for aragodbpedia took 39705.68550944328s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.36465334892273s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.7196612358093262s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.744529724121094e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for archiveshub-linkeddata took 85.18515157699585s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.3392181396484375e-05s
Availability | VoID file availability check for Archivi ISMA took 0.00032973289489746094s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.2964937686920166s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.0209200382232666s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.0279159545898438e-05s
Believability | Calculation of trust value for Archivi ISMA took 8.344650268554688e-06s
INFO | --- Analysis for archivio-isma took 5.598711252212524s
Availability | SPARQL endpoint availability check for ARIADNE took 5.602836608886719e-05s
Availability | VoID file availability check for ARIADNE took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2580714225769043s
Reputation | Calculation of the PageRank for ARIADNE took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.0994415283203125e-05s
Believability | Calculation of trust value for ARIADNE took 7.867813110351562e-06s
INFO | --- Analysis for ariadne took 3.7701025009155273s
Availability | SPARQL endpoint availability check for Aristotle University took 4.2438507080078125e-05s
Availability | VoID file availability check for Aristotle University took 0.0002982616424560547s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.2593369483947754s
Reputation | Calculation of the PageRank for Aristotle University took 0.020920515060424805s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 4.76837158203125e-05s
Believability | Calculation of trust value for Aristotle University took 8.344650268554688e-06s
INFO | --- Analysis for aristotle-university took 3.313246965408325s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.219094276428223s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2555222511291504s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.218650817871094e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 8.106231689453125e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 21.467854738235474s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.220008850097656e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.25295233726501465s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.021155357360839844s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0008459091186523438s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.409385681152344e-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 3.337550640106201s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.938903331756592s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.269773006439209s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.719329833984375e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 6.9141387939453125e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 17.955623149871826s
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.0006573200225830078s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.25690388679504395s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0008146762847900391s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010895729064941406s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 8.906169414520264s
Availability | SPARQL endpoint availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 4.315376281738281e-05s
Availability | VoID file availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.2559194564819336s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.2159347534179688e-05s
Believability | Calculation of trust value for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 8.106231689453125e-06s
INFO | --- Analysis for Arthron took 2.3891189098358154s
Availability | SPARQL endpoint availability check for Arthroscopy community took 7.677078247070312e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2700674533843994s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010514259338378906s
Believability | Calculation of trust value for Arthroscopy community took 7.867813110351562e-06s
INFO | --- Analysis for arthroscopy took 43.87860727310181s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 1.756831407546997s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0005645751953125s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 0.08054947853088379s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 0.0825655460357666s
Versatility | Languages check for Wikidata entry for Art × Science International took 0.09397506713867188s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 0.09372949600219727s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.08290767669677734s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.09413886070251465s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.09444808959960938s
License | MR license check for Wikidata entry for Art × Science International took 0.09250760078430176s
License | HR license check for Wikidata entry for Art × Science International took 0.09380316734313965s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.08309292793273926s
Understandability | Number of label check for Wikidata entry for Art × Science International took 0.0721430778503418s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.16000103950500488s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.08275461196899414s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.08110690116882324s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.07147741317749023s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 0.0001366138458251953s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.09162139892578125s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.0817413330078125s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.09463214874267578s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.07193708419799805s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.07179021835327148s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.17472076416015625s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.16290855407714844s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 0.16372346878051758s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.09434080123901367s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.08184933662414551s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 0.08039140701293945s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 1.4521980285644531s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 0.0001475811004638672s
Security | Sign check for Wikidata entry for Art × Science International took 0.08035635948181152s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.2794315814971924s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.3589859008789062e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 4.76837158203125e-07s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 7.3909759521484375e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 21.528767585754395s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.750760316848755s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2669799327850342s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.82012939453125e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 13.080442190170288s
Availability | SPARQL endpoint availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 2.386147975921631s
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.0006844997406005859s
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.7674705982208252s
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.03313469886779785s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.001392364501953125s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.00012087821960449219s
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 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 11.604558944702148s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.384734869003296s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.26981139183044434s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.96453857421875e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 12.107851028442383s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.3872480392456055s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.00036787986755371094s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2760457992553711s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02094554901123047s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.8160552978515625e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-CRB took 14.296607494354248s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.40102219581604s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.27106213569641113s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.00010800361633300781s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.59528660774231s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.383848190307617s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.29123425483703613s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-DQOT took 12.694782495498657s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.4019742012023926s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0004031658172607422s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2635691165924072s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.702278137207031e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.2636184692382812e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.711563110351562s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 6.651108503341675s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.28289103507995605s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020825862884521484s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0008661746978759766s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.726119995117188e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 17.032176733016968s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.3897311687469482s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.27320241928100586s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020654678344726562s
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.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.1021575927734375e-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.7220458984375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 12.146639823913574s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.3949596881866455s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.27976250648498535s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020792007446289062s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.364418029785156e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.64978814125061s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.067003965377808s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.25526857376098633s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0220487117767334s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0008816719055175781s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.175041198730469e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 16.118497610092163s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.397853374481201s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007920265197753906s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2620842456817627s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.724761962890625e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 11.115212202072144s
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.397189140319824s
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.0006935596466064453s
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.29865360260009766s
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.021286725997924805s
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.7404556274414062e-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.001110076904296875s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.00010061264038085938s
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 9.059906005859375e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.84245252609253s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.4133033752441406s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.2617819309234619s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.0208895206451416s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.673004150390625e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC_-_DNB took 11.067895412445068s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.363059997558594e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2687709331512451s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.05718994140625e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.1920928955078125e-05s
INFO | --- Analysis for asit took 8.52703046798706s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.3392181396484375e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2661619186401367s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.000720977783203125s
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 6.9141387939453125e-06s
INFO | --- Analysis for asjp took 5.5490522384643555s
Availability | SPARQL endpoint availability check for ASN:US took 0.11088299751281738s
Availability | VoID file availability check for ASN:US took 0.00032901763916015625s
Completeness | Calculation of interlinking completeness for ASN:US took 0.27383875846862793s
Reputation | Calculation of the PageRank for ASN:US took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for ASN:US took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.604194641113281e-05s
Believability | Calculation of trust value for ASN:US took 5.245208740234375e-06s
INFO | --- Analysis for asn-us took 6.64944863319397s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 5.245208740234375e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.001234292984008789s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.28184080123901367s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020379066467285156s
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.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.9087066650390625e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 6.198883056640625e-06s
INFO | --- Analysis for aspire-mmu took 4.748546600341797s
Availability | SPARQL endpoint availability check for associations took 4.315376281738281e-05s
Availability | VoID file availability check for associations took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for associations took 0.27843523025512695s
Reputation | Calculation of the PageRank for associations took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for associations took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for associations took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for associations took 6.508827209472656e-05s
Believability | Calculation of trust value for associations took 1.1920928955078125e-05s
INFO | --- Analysis for associations took 7.265847444534302s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 5.6743621826171875e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2657928466796875s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.6941299438476562e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 1.0967254638671875e-05s
INFO | --- Analysis for atc-publikovan--s-kl took 2.9536783695220947s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.482269287109375e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.26077771186828613s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.940696716308594e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 6.9141387939453125e-06s
INFO | --- Analysis for athelia-rfid took 4.097221851348877s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.124641418457031e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2654540538787842s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.0013580322265625e-05s
INFO | --- Analysis for aueb-linked-open-data took 2.968721389770508s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 59.54599213600159s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.26833319664001465s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.555152893066406e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for AugustiniConfessiones took 62.918053150177s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6912484169006348s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.27301764488220215s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.107589721679688e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 9.059906005859375e-06s
INFO | --- Analysis for austrian_ski_racers took 3.8221163749694824s
Availability | SPARQL endpoint availability check for AVsOnto took 4.4345855712890625e-05s
Availability | VoID file availability check for AVsOnto took 0.0011785030364990234s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.25613903999328613s
Reputation | Calculation of the PageRank for AVsOnto took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.0279159545898438e-05s
Believability | Calculation of trust value for AVsOnto took 1.0728836059570312e-05s
INFO | --- Analysis for AVsOnto took 3.237325668334961s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23963642120361328s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00027441978454589844s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 173.77365851402283s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5368833541870117s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06473875045776s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 205.25083422660828s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1045310497284s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.09882164001465s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2424783706665039s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24179387092590332s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1674816608428955s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12320423126220703s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 52.893189668655396s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.08955359458923s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1568746566772461s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 193.62518978118896s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2477107048034668s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1165018081665039s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11571097373962402s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09916114807128906s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.78646183013916s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00011134147644042969s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09677982330322266s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.08420276641846s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1665349006652832s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10597729682922363s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13793325424194336s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2405107021331787s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24297666549682617s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 450.89459133148193s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18178892135620117s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 33.952868938446045s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.27108097076416s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.839875221252441s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1408534049987793s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.11888790130615s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 164.3115553855896s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.5590932369232178s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.50232005119324s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.8236045837402344s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15081024169921875s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.705159902572632s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.723853349685669s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.02139735221862793s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6689300537109375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 6.198883056640625e-06s
INFO | --- Analysis for b3kat took 4037.9132809638977s
Availability | SPARQL endpoint availability check for BabelNet took 0.6338872909545898s
Availability | VoID file availability check for BabelNet took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for BabelNet took 0.25800132751464844s
Reputation | Calculation of the PageRank for BabelNet took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00016570091247558594s
Believability | Calculation of trust value for BabelNet took 7.867813110351562e-06s
INFO | --- Analysis for babelnet took 6.245653867721558s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.2438507080078125e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.7013804912567139s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020804405212402344s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bacevicius.lt took 7.3909759521484375e-06s
INFO | --- Analysis for Bacevicius.lt took 3.237401247024536s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5481588840484619s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.25170183181762695s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.506111145019531e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 7.62939453125e-06s
INFO | --- Analysis for bag took 4.42925500869751s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.8666598796844482s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.27022767066955566s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0994415283203125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 8.344650268554688e-06s
INFO | --- Analysis for baixue took 3.2611167430877686s
Availability | SPARQL endpoint availability check for baixue composer took 4.506111145019531e-05s
Availability | VoID file availability check for baixue composer took 0.0014920234680175781s
Completeness | Calculation of interlinking completeness for baixue composer took 0.2780184745788574s
Reputation | Calculation of the PageRank for baixue composer took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.0279159545898438e-05s
Believability | Calculation of trust value for baixue composer took 1.2874603271484375e-05s
INFO | --- Analysis for baixue_composer took 3.2023162841796875s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.506111145019531e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.000701904296875s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.25269627571105957s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.9802322387695312e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 8.106231689453125e-06s
INFO | --- Analysis for baixue_imagery took 2.9915518760681152s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.4345855712890625e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.25878095626831055s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.86102294921875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.3909759521484375e-06s
INFO | --- Analysis for baixue_imagery1 took 3.2904655933380127s
Availability | SPARQL endpoint availability check for BAMS took 4.291534423828125e-05s
Availability | VoID file availability check for BAMS took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for BAMS took 0.26647448539733887s
Reputation | Calculation of the PageRank for BAMS took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for BAMS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for BAMS took 2.9087066650390625e-05s
Believability | Calculation of trust value for BAMS took 1.0251998901367188e-05s
INFO | --- Analysis for bams took 2.9318997859954834s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.5299530029296875e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.26401352882385254s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.719329833984375e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 7.3909759521484375e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 2.9219484329223633s
Availability | SPARQL endpoint availability check for BBC Music took 0.29819488525390625s
Availability | VoID file availability check for BBC Music took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for BBC Music took 0.26958441734313965s
Reputation | Calculation of the PageRank for BBC Music took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013327598571777344s
Believability | Calculation of trust value for BBC Music took 6.9141387939453125e-06s
INFO | --- Analysis for bbc-music took 3.282130002975464s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.3960535526275635s
Availability | VoID file availability check for BBC Programmes took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2694253921508789s
Reputation | Calculation of the PageRank for BBC Programmes took 0.02131056785583496s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010085105895996094s
Believability | Calculation of trust value for BBC Programmes took 6.9141387939453125e-06s
INFO | --- Analysis for bbc-programmes took 11.39940881729126s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.25320887565612793s
Availability | VoID file availability check for BBC Wildlife Finder took 0.00075531005859375s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2867465019226074s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010442733764648438s
Believability | Calculation of trust value for BBC Wildlife Finder took 7.62939453125e-06s
INFO | --- Analysis for bbc-wildlife-finder took 10.468839168548584s
Availability | SPARQL endpoint availability check for BBOP took 4.3392181396484375e-05s
Availability | VoID file availability check for BBOP took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for BBOP took 0.2682013511657715s
Reputation | Calculation of the PageRank for BBOP took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for BBOP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.7894973754882812e-05s
Believability | Calculation of trust value for BBOP took 7.62939453125e-06s
INFO | --- Analysis for bbop took 2.855175733566284s
Availability | SPARQL endpoint availability check for BBOP took 4.410743713378906e-05s
Availability | VoID file availability check for BBOP took 0.0009946823120117188s
Completeness | Calculation of interlinking completeness for BBOP took 0.2592334747314453s
Reputation | Calculation of the PageRank for BBOP took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for BBOP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.0279159545898438e-05s
Believability | Calculation of trust value for BBOP took 6.9141387939453125e-06s
INFO | --- Analysis for bbop-selected took 21.209139823913574s
Availability | SPARQL endpoint availability check for Bdgp took 1.5494725704193115s
Availability | VoID file availability check for Bdgp took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2701249122619629s
Reputation | Calculation of the PageRank for Bdgp took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Bdgp took 2.8133392333984375e-05s
Believability | Calculation of trust value for Bdgp took 7.867813110351562e-06s
INFO | --- Analysis for bdgp took 8.857620477676392s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.291534423828125e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.26360416412353516s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bendev Junior took 8.106231689453125e-06s
INFO | --- Analysis for bendevoficial took 5.242686748504639s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.304782390594482s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.25182604789733887s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.604194641113281e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 4.76837158203125e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 11.615843296051025s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.1961669921875e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.2720160484313965s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 2.956390380859375e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 7.867813110351562e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.9274749755859375s
Availability | SPARQL endpoint availability check for berlios took 5.507469177246094e-05s
Availability | VoID file availability check for berlios took 0.00034809112548828125s
Completeness | Calculation of interlinking completeness for berlios took 0.2637939453125s
Reputation | Calculation of the PageRank for berlios took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for berlios took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for berlios took 8.58306884765625e-05s
Believability | Calculation of trust value for berlios took 7.152557373046875e-06s
INFO | --- Analysis for berlios took 2.6068572998046875s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.4345855712890625e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3043935298919678s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020305871963500977s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.556510925292969e-05s
Believability | Calculation of trust value for Between Our Worlds took 8.58306884765625e-06s
INFO | --- Analysis for betweenourworlds took 9.089364767074585s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.48128533363342285s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.28213953971862793s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.202957153320312e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for bfs-linked-data took 3.0488312244415283s
Availability | SPARQL endpoint availability check for BibBase took 0.10093092918395996s
Availability | VoID file availability check for BibBase took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for BibBase took 0.2585594654083252s
Reputation | Calculation of the PageRank for BibBase took 0.02121114730834961s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.489059448242188e-05s
Believability | Calculation of trust value for BibBase took 7.3909759521484375e-06s
INFO | --- Analysis for bibbase took 2.518523693084717s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 6.699562072753906e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.25921082496643066s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.001003265380859375s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.0001232624053955078s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 7.867813110351562e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 6.793858766555786s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.38690185546875e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.25138044357299805s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020716428756713867s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010061264038085938s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.3113021850585938e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 11.224910736083984s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.2438507080078125e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.25677990913391113s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.719329833984375e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.8987350463867188s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.220008850097656e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2476367950439453s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.409385681152344e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 7.62939453125e-06s
INFO | --- Analysis for BibSonomy took 9.46501874923706s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 7.772445678710938e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.26537418365478516s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.02106451988220215s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.361701965332031e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 7.3909759521484375e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.115518569946289s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.506111145019531e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2781393527984619s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020915508270263672s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 7.62939453125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.574267864227295s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 5.507469177246094e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.2759382724761963s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.838539123535156e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.977591037750244s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 2.1774373054504395s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006635189056396484s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 38.42180776596069s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5149965286254883s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.56140637397766s
Interoperability | New terms check for Bio2RDF::Affymetrix took 41.21589279174805s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.140645027160645s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.14409470558166504s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 1.0070106983184814s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.27623581886291504s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 6.170608282089233s
License | MR license check for Bio2RDF::Affymetrix took 0.505051851272583s
License | HR license check for Bio2RDF::Affymetrix took 60.09058094024658s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.15755200386047363s
Understandability | Number of label check for Bio2RDF::Affymetrix took 10.219639778137207s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.44062066078186035s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.15634584426879883s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.20122814178466797s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.1435091495513916s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.57250428199768s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 75.93134236335754s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.7416024208068848s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2931818962097168s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.8668689727783203s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.19551897048950195s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.12035608291625977s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.29426050186157227s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.2650434970855713s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 120.56025910377502s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 213.6755566596985s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.6037337779998779s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.16167140007019043s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.13993287086486816s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 18.771303176879883s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.904921293258667s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6607625484466553s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.3555586338043213s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 69.95741534233093s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.2976839542388916s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 11.933609008789062s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3379898071289062s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.45196771621704s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.6981520652770996s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.36376452445983887s
Security | Sign check for Bio2RDF::Affymetrix took 0.13589000701904297s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 12.248844385147095s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.8230915069580078s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.021091461181640625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010180473327636719s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 210.72187328338623s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 1490.2983355522156s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.6295959949493408s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0007212162017822266s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 34.42010307312012s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2623169422149658s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 44.07955288887024s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.53554725646973s
Versatility | Languages check for Bio2RDF::Biomodels took 60.235456228256226s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2570786476135254s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.14413070678710938s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.8820304870605469s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.3609588146209717s
Availability | RDF dump link check for Bio2RDF::Biomodels took 6.385247468948364s
License | MR license check for Bio2RDF::Biomodels took 0.5788226127624512s
License | HR license check for Bio2RDF::Biomodels took 60.251126289367676s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.27076172828674316s
Understandability | Number of label check for Bio2RDF::Biomodels took 11.223240852355957s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.6022999286651611s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.26522088050842285s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.27903079986572266s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.2614603042602539s
Performance | Throughput check for Bio2RDF::Biomodels took 11.091458320617676s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 74.69983291625977s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 2.734661817550659s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.4190950393676758s
Interlinking | skos check for Bio2RDF::Biomodels took 0.9093048572540283s
Interlinking | skos check for Bio2RDF::Biomodels took 0.35474395751953125s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2982041835784912s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5358724594116211s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5317144393920898s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 119.95090341567993s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 20.679628133773804s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.42374634742736816s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.28348708152770996s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2864668369293213s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 18.641584157943726s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8939402103424072s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6810312271118164s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.5209667682647705s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 70.564950466156s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.4445018768310547s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 12.171887159347534s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3393185138702393s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.605767011642456s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.6981983184814453s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.7342109680175781s
Security | Sign check for Bio2RDF::Biomodels took 0.2799112796783447s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 11.502737522125244s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 1.3903179168701172s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011777877807617188s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 59.7805962562561s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1152.7714564800262s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.4345855712890625e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.2705984115600586s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.24249267578125e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 4.197064399719238s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.5892469882965088s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0007865428924560547s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 38.090389251708984s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2427899837493896s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 46.40831160545349s
Interoperability | New terms check for Bio2RDF::Bioportal took 41.77618932723999s
Versatility | Languages check for Bio2RDF::Bioportal took 60.247100830078125s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2723972797393799s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.1676633358001709s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 1.0288541316986084s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3301558494567871s
Availability | RDF dump link check for Bio2RDF::Bioportal took 6.291471719741821s
License | MR license check for Bio2RDF::Bioportal took 0.652660608291626s
License | HR license check for Bio2RDF::Bioportal took 60.24721598625183s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.3042871952056885s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.51958966255188s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5789632797241211s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2730073928833008s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2686948776245117s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.2541646957397461s
Performance | Throughput check for Bio2RDF::Bioportal took 11.104657888412476s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 74.25870561599731s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.27472829818725586s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.4313337802886963s
Interlinking | skos check for Bio2RDF::Bioportal took 0.9653797149658203s
Interlinking | skos check for Bio2RDF::Bioportal took 0.43721795082092285s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.24855971336364746s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5675058364868164s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5327239036560059s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 119.45710325241089s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 144.5811321735382s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.8465805053710938s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.30919957160949707s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.28870511054992676s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 19.258211851119995s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.9269382953643799s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6595137119293213s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.5187966823577881s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 70.41329574584961s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.413719892501831s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 11.877782106399536s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3509681224822998s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.61167573928833s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7014932632446289s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.43829822540283203s
Security | Sign check for Bio2RDF::Bioportal took 0.3030877113342285s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 11.627930641174316s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 1.266420602798462s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02746129035949707s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004165172576904297s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 149.82730150222778s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-bioportal took 1378.3475544452667s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.14644837379455566s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.283416748046875s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.078315734863281e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-chembl took 17.50330901145935s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.6094403266906738s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0005953311920166016s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 34.96718978881836s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.244899034500122s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 44.05427527427673s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 43.50086736679077s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.24448251724243s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.26607823371887207s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.17169475555419922s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 1.0428791046142578s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.3548409938812256s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 6.341928482055664s
License | MR license check for Bio2RDF::Clinicaltrials took 0.7088909149169922s
License | HR license check for Bio2RDF::Clinicaltrials took 60.23905396461487s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.2666921615600586s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.495729207992554s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.6044156551361084s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.2709691524505615s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2692391872406006s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.264660120010376s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 10.623743534088135s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 73.89285731315613s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.9000153541564941s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.4167330265045166s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 1.1594691276550293s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.34992384910583496s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2754344940185547s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5365898609161377s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5011603832244873s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 122.38757348060608s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 62.19150638580322s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.4397618770599365s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2947652339935303s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.29899096488952637s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 19.52346634864807s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8964791297912598s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6928346157073975s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.5101306438446045s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 69.98684501647949s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.4852733612060547s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 11.774107217788696s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3481807708740234s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.67066407203674s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7174985408782959s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.7837514877319336s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2805931568145752s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 11.542455434799194s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.8511595726013184s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.021237611770629883s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 167.92959451675415s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1302.8107507228851s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.5995945930480957s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0006530284881591797s
Extra | Recovery of all triples for Bio2RDF::Ctd took 37.61454963684082s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.243462324142456s
Amount of data | Number of triples check for Bio2RDF::Ctd took 43.912407875061035s
Interoperability | New terms check for Bio2RDF::Ctd took 42.63439965248108s
Versatility | Languages check for Bio2RDF::Ctd took 60.2828426361084s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.26889610290527344s
Security | Check HTTPS for Bio2RDF::Ctd took 0.157548189163208s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.9755721092224121s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3315291404724121s
Availability | RDF dump link check for Bio2RDF::Ctd took 6.348026275634766s
License | MR license check for Bio2RDF::Ctd took 0.7319021224975586s
License | HR license check for Bio2RDF::Ctd took 60.24943208694458s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2713453769683838s
Understandability | Number of label check for Bio2RDF::Ctd took 10.484586954116821s
Understandability | URI regex check for Bio2RDF::Ctd took 0.6164522171020508s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.24647188186645508s
Verifiability | Authors check for Bio2RDF::Ctd took 0.26684021949768066s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.25746917724609375s
Performance | Throughput check for Bio2RDF::Ctd took 11.425087928771973s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 72.00304961204529s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.26604604721069336s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.3448605537414551s
Interlinking | skos check for Bio2RDF::Ctd took 0.7967555522918701s
Interlinking | skos check for Bio2RDF::Ctd took 0.3774902820587158s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2729148864746094s
Currency | Creation date check for Bio2RDF::Ctd took 0.5394744873046875s
Currency | Modification date check for Bio2RDF::Ctd took 0.531012773513794s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 122.83909869194031s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 118.34205150604248s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.7110130786895752s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.28155946731567383s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.3035433292388916s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 20.23791241645813s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.9023246765136719s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6872608661651611s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.48635196685791016s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 71.06708860397339s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.4713802337646484s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 12.114840507507324s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.379612684249878s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.59182620048523s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7052290439605713s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.4465909004211426s
Security | Sign check for Bio2RDF::Ctd took 0.29100728034973145s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 8.98967170715332s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.9732885360717773s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.022725820541381836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 7.414817810058594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 108.94677662849426s
Believability | Calculation of trust value for Bio2RDF::Ctd took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-ctd took 1306.8748016357422s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 5.078315734863281e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0008170604705810547s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.690727710723877s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021050214767456055s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.5789947509765625e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-dataset took 4.298880100250244s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.5971918106079102s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005943775177001953s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 36.68224906921387s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2339096069335938s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.66589975357056s
Interoperability | New terms check for Bio2RDF::Dbsnp took 41.225857734680176s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.237948417663574s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.27202606201171875s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1566629409790039s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.8472175598144531s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.36400675773620605s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 6.391865015029907s
License | MR license check for Bio2RDF::Dbsnp took 0.6930670738220215s
License | HR license check for Bio2RDF::Dbsnp took 60.25887155532837s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.28894519805908203s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.841399431228638s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5693247318267822s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.25952911376953125s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2635471820831299s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.26447248458862305s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.452500104904175s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 77.7855441570282s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.7072341442108154s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3754439353942871s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.7913737297058105s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.36109089851379395s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.27511167526245117s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5238847732543945s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5171258449554443s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 120.00689458847046s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 135.1995038986206s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4314243793487549s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2931208610534668s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2903733253479004s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 18.14340043067932s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.9105911254882812s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6662755012512207s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.3963449001312256s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 70.3866593837738s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.823585271835327s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 11.236827373504639s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3689427375793457s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.66736054420471s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7187976837158203s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.47188711166381836s
Security | Sign check for Bio2RDF::Dbsnp took 0.27902841567993164s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 11.574099779129028s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 1.5048413276672363s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 69.86096572875977s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1277.6316406726837s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.5912582874298096s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006527900695800781s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 35.86664366722107s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2730937004089355s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 44.42157506942749s
Interoperability | New terms check for Bio2RDF::Drugbank took 42.01971983909607s
Versatility | Languages check for Bio2RDF::Drugbank took 60.2295401096344s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.3141744136810303s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.14785242080688477s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 1.0103750228881836s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3396108150482178s
Availability | RDF dump link check for Bio2RDF::Drugbank took 6.2387940883636475s
License | MR license check for Bio2RDF::Drugbank took 0.5618917942047119s
License | HR license check for Bio2RDF::Drugbank took 60.24837803840637s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2770364284515381s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.23042893409729s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5994765758514404s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2676398754119873s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.26723551750183105s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2805624008178711s
Performance | Throughput check for Bio2RDF::Drugbank took 10.761539459228516s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 73.89543080329895s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.7126374244689941s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.40685153007507324s
Interlinking | skos check for Bio2RDF::Drugbank took 1.1392738819122314s
Interlinking | skos check for Bio2RDF::Drugbank took 0.3602783679962158s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.26209259033203125s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5453042984008789s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5373170375823975s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 123.38075041770935s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 116.76673555374146s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4314589500427246s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.27922487258911133s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2632718086242676s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 17.624985933303833s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8955681324005127s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.658261775970459s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.41348886489868164s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 70.03938484191895s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.717383623123169s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 11.197843790054321s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3771436214447021s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.60118627548218s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7071068286895752s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.4420020580291748s
Security | Sign check for Bio2RDF::Drugbank took 0.3039054870605469s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 11.876097202301025s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.9350330829620361s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020751953125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 76.26427173614502s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1259.6573300361633s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.5929667949676514s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006814002990722656s
Extra | Recovery of all triples for Bio2RDF::Genage took 34.682677268981934s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2660388946533203s
Amount of data | Number of triples check for Bio2RDF::Genage took 44.53462290763855s
Interoperability | New terms check for Bio2RDF::Genage took 44.92213463783264s
Versatility | Languages check for Bio2RDF::Genage took 60.229583740234375s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2694878578186035s
Security | Check HTTPS for Bio2RDF::Genage took 0.16652202606201172s
Interpretability | RDF structures check for Bio2RDF::Genage took 1.494950532913208s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3270740509033203s
Availability | RDF dump link check for Bio2RDF::Genage took 6.265807390213013s
License | MR license check for Bio2RDF::Genage took 0.551232099533081s
License | HR license check for Bio2RDF::Genage took 60.244264125823975s
Amount of data | Number of property check for Bio2RDF::Genage took 0.31386852264404297s
Understandability | Number of label check for Bio2RDF::Genage took 10.784269332885742s
Understandability | URI regex check for Bio2RDF::Genage took 0.5522098541259766s
Understandability | Vocabs check for Bio2RDF::Genage took 0.25734877586364746s
Verifiability | Authors check for Bio2RDF::Genage took 0.29369235038757324s
Verifiability | Publishers check for Bio2RDF::Genage took 0.28214168548583984s
Performance | Throughput check for Bio2RDF::Genage took 11.314229726791382s
Amount of data | Check the number of entities for Bio2RDF::Genage took 74.69668889045715s
Verifiability | Contribs. check for Bio2RDF::Genage took 2.9483492374420166s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.40980076789855957s
Interlinking | skos check for Bio2RDF::Genage took 1.0263302326202393s
Interlinking | skos check for Bio2RDF::Genage took 0.35930347442626953s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2644946575164795s
Currency | Creation date check for Bio2RDF::Genage took 0.5417358875274658s
Currency | Modification date check for Bio2RDF::Genage took 0.5449755191802979s
Rep.Conc. | URIs length for Bio2RDF::Genage took 121.79929089546204s
Interoperability | New vocabularies check for Bio2RDF::Genage took 24.557979583740234s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.47255945205688477s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.27295589447021484s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.27899646759033203s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 18.851621389389038s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.9007232189178467s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.7030637264251709s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.49500322341918945s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 70.99337911605835s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.4222965240478516s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 12.294117450714111s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3463308811187744s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.59891128540039s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7169363498687744s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 1.4738545417785645s
Security | Sign check for Bio2RDF::Genage took 0.2781562805175781s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 11.518733501434326s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 1.4135539531707764s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.175041198730469e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-genage took 1187.954833984375s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.2954585552215576s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020721435546875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.8650970458984375e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-genbank took 4.675557374954224s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.6005926132202148s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0005688667297363281s
Extra | Recovery of all triples for Bio2RDF::Gendr took 38.43067789077759s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2792723178863525s
Amount of data | Number of triples check for Bio2RDF::Gendr took 43.42848753929138s
Interoperability | New terms check for Bio2RDF::Gendr took 41.37742614746094s
Versatility | Languages check for Bio2RDF::Gendr took 60.24132561683655s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.26676392555236816s
Security | Check HTTPS for Bio2RDF::Gendr took 0.14593005180358887s
Interpretability | RDF structures check for Bio2RDF::Gendr took 1.5614361763000488s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.3277266025543213s
Availability | RDF dump link check for Bio2RDF::Gendr took 6.204836845397949s
License | MR license check for Bio2RDF::Gendr took 0.7319941520690918s
License | HR license check for Bio2RDF::Gendr took 60.2392373085022s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.26134777069091797s
Understandability | Number of label check for Bio2RDF::Gendr took 9.776913404464722s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5760421752929688s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2652556896209717s
Verifiability | Authors check for Bio2RDF::Gendr took 0.28379249572753906s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2634620666503906s
Performance | Throughput check for Bio2RDF::Gendr took 10.764351606369019s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 75.31640815734863s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.886150598526001s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.4128232002258301s
Interlinking | skos check for Bio2RDF::Gendr took 0.9706668853759766s
Interlinking | skos check for Bio2RDF::Gendr took 0.34677672386169434s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.26958727836608887s
Currency | Creation date check for Bio2RDF::Gendr took 0.5424017906188965s
Currency | Modification date check for Bio2RDF::Gendr took 0.5351536273956299s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 118.72798180580139s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 23.154422998428345s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.42931127548217773s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.28238463401794434s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.29723167419433594s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 18.48314142227173s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.903714656829834s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6636536121368408s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.47197890281677246s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 70.56170225143433s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4531984329223633s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 11.633362531661987s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.39918851852417s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.61494040489197s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.701650857925415s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 1.24623441696167s
Security | Sign check for Bio2RDF::Gendr took 0.26067161560058594s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 11.758969783782959s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.843895673751831s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 106.89517331123352s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-gendr took 1203.4848861694336s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.5955996513366699s
Availability | VoID file availability check for Bio2RDF::Goa took 0.00039005279541015625s
Extra | Recovery of all triples for Bio2RDF::Goa took 36.921650409698486s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2676477432250977s
Amount of data | Number of triples check for Bio2RDF::Goa took 44.459956407547s
Interoperability | New terms check for Bio2RDF::Goa took 42.00323557853699s
Versatility | Languages check for Bio2RDF::Goa took 60.238556146621704s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.2503025531768799s
Security | Check HTTPS for Bio2RDF::Goa took 0.1460282802581787s
Interpretability | RDF structures check for Bio2RDF::Goa took 1.0137007236480713s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3378145694732666s
Availability | RDF dump link check for Bio2RDF::Goa took 6.34760856628418s
License | MR license check for Bio2RDF::Goa took 0.6063368320465088s
License | HR license check for Bio2RDF::Goa took 60.27078151702881s
Amount of data | Number of property check for Bio2RDF::Goa took 0.3056786060333252s
Understandability | Number of label check for Bio2RDF::Goa took 10.701382398605347s
Understandability | URI regex check for Bio2RDF::Goa took 0.5565288066864014s
Understandability | Vocabs check for Bio2RDF::Goa took 0.27223873138427734s
Verifiability | Authors check for Bio2RDF::Goa took 0.29393625259399414s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2563052177429199s
Performance | Throughput check for Bio2RDF::Goa took 11.274319887161255s
Amount of data | Check the number of entities for Bio2RDF::Goa took 72.64228367805481s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.28182315826416016s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.43338632583618164s
Interlinking | skos check for Bio2RDF::Goa took 0.9711306095123291s
Interlinking | skos check for Bio2RDF::Goa took 0.5089526176452637s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2876572608947754s
Currency | Creation date check for Bio2RDF::Goa took 0.5587911605834961s
Currency | Modification date check for Bio2RDF::Goa took 0.5300807952880859s
Rep.Conc. | URIs length for Bio2RDF::Goa took 120.60900664329529s
Interoperability | New vocabularies check for Bio2RDF::Goa took 24.120527505874634s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.4934697151184082s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2562534809112549s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.2674405574798584s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 17.21538519859314s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.9001052379608154s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6687667369842529s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.7867915630340576s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 70.94140982627869s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.444533109664917s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 12.551609516143799s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.4140536785125732s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.61242938041687s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.702129602432251s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.4321162700653076s
Security | Sign check for Bio2RDF::Goa took 0.2720167636871338s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 11.492682456970215s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.817990779876709s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 92.97642397880554s
Believability | Calculation of trust value for Bio2RDF::Goa took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-goa took 1190.823706150055s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.5908634662628174s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006444454193115234s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 33.14021110534668s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2785146236419678s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 44.24176645278931s
Interoperability | New terms check for Bio2RDF::Hgnc took 44.7078742980957s
Versatility | Languages check for Bio2RDF::Hgnc took 60.25495433807373s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2723367214202881s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.15721416473388672s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 1.0431015491485596s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.33405113220214844s
Availability | RDF dump link check for Bio2RDF::Hgnc took 6.435428142547607s
License | MR license check for Bio2RDF::Hgnc took 0.7150659561157227s
License | HR license check for Bio2RDF::Hgnc took 60.2364284992218s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.25429439544677734s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.141757726669312s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5721893310546875s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.2610759735107422s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.26500725746154785s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.25678348541259766s
Performance | Throughput check for Bio2RDF::Hgnc took 11.42884111404419s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 73.48479008674622s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.7088043689727783s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3327465057373047s
Interlinking | skos check for Bio2RDF::Hgnc took 1.1409950256347656s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3401176929473877s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2644517421722412s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5280232429504395s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5540883541107178s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 122.30955290794373s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 122.41973233222961s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.45328330993652344s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.29400205612182617s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.3124709129333496s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 17.58997392654419s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8951356410980225s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6580963134765625s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.5027482509613037s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 71.34618949890137s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 4.389594793319702s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 12.365435600280762s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.359123945236206s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.58474540710449s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7124111652374268s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.439316987991333s
Security | Sign check for Bio2RDF::Hgnc took 0.27599310874938965s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 9.540698051452637s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 1.457103967666626s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00010418891906738281s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 185.9691185951233s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1379.9158775806427s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.6113109588623047s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006253719329833984s
Extra | Recovery of all triples for Bio2RDF::Homologene took 34.91524910926819s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.3136911392211914s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.96449637413025s
Interoperability | New terms check for Bio2RDF::Homologene took 43.59309244155884s
Versatility | Languages check for Bio2RDF::Homologene took 60.256988525390625s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.26731157302856445s
Security | Check HTTPS for Bio2RDF::Homologene took 0.14583492279052734s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.9600541591644287s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.33199191093444824s
Availability | RDF dump link check for Bio2RDF::Homologene took 6.370458364486694s
License | MR license check for Bio2RDF::Homologene took 0.5110571384429932s
License | HR license check for Bio2RDF::Homologene took 60.254581928253174s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.25522589683532715s
Understandability | Number of label check for Bio2RDF::Homologene took 10.543798685073853s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5770018100738525s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.27401113510131836s
Verifiability | Authors check for Bio2RDF::Homologene took 0.27239131927490234s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.2614309787750244s
Performance | Throughput check for Bio2RDF::Homologene took 11.538822650909424s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 74.23727917671204s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.7041237354278564s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.35030460357666016s
Interlinking | skos check for Bio2RDF::Homologene took 1.03446364402771s
Interlinking | skos check for Bio2RDF::Homologene took 0.386610746383667s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.2656741142272949s
Currency | Creation date check for Bio2RDF::Homologene took 0.5387194156646729s
Currency | Modification date check for Bio2RDF::Homologene took 0.5184004306793213s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 121.00359654426575s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 198.28290700912476s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.744884729385376s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2844507694244385s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.32601308822631836s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 18.334787130355835s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.902956485748291s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6725239753723145s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.5384528636932373s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 72.31285572052002s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4627411365509033s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 11.677978277206421s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3787791728973389s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.62263369560242s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7057642936706543s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.4600667953491211s
Security | Sign check for Bio2RDF::Homologene took 0.298351526260376s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 12.316768169403076s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 1.0203192234039307s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.026670455932617188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0010488033294677734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 76.81834292411804s
Believability | Calculation of trust value for Bio2RDF::Homologene took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-homologene took 1349.2789356708527s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 7.390975952148438e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.2505342960357666s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.02120041847229004s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-inoh took 4.559406042098999s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.5931921005249023s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006282329559326172s
Extra | Recovery of all triples for Bio2RDF::Interpro took 38.39858055114746s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2792530059814453s
Amount of data | Number of triples check for Bio2RDF::Interpro took 43.984522581100464s
Interoperability | New terms check for Bio2RDF::Interpro took 43.923917293548584s
Versatility | Languages check for Bio2RDF::Interpro took 60.24833631515503s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.26119327545166016s
Security | Check HTTPS for Bio2RDF::Interpro took 0.1578068733215332s
Interpretability | RDF structures check for Bio2RDF::Interpro took 1.4206922054290771s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.3536694049835205s
Availability | RDF dump link check for Bio2RDF::Interpro took 6.278209924697876s
License | MR license check for Bio2RDF::Interpro took 0.6291120052337646s
License | HR license check for Bio2RDF::Interpro took 60.2794668674469s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2566568851470947s
Understandability | Number of label check for Bio2RDF::Interpro took 10.586972713470459s
Understandability | URI regex check for Bio2RDF::Interpro took 0.582953929901123s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.25239014625549316s
Verifiability | Authors check for Bio2RDF::Interpro took 0.27883076667785645s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.27337050437927246s
Performance | Throughput check for Bio2RDF::Interpro took 10.22139835357666s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 76.75548839569092s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.42893481254577637s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.37470006942749023s
Interlinking | skos check for Bio2RDF::Interpro took 0.7740945816040039s
Interlinking | skos check for Bio2RDF::Interpro took 0.35286736488342285s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2655758857727051s
Currency | Creation date check for Bio2RDF::Interpro took 0.5366926193237305s
Currency | Modification date check for Bio2RDF::Interpro took 0.5155107975006104s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 122.25286650657654s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 20.086881399154663s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4420199394226074s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2823786735534668s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.294633150100708s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 18.897910118103027s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8994789123535156s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6641297340393066s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.6558163166046143s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 70.6576669216156s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.444540023803711s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 11.984634637832642s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.404115915298462s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.58894467353821s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.702817440032959s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.8055522441864014s
Security | Sign check for Bio2RDF::Interpro took 0.2737083435058594s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 12.694764852523804s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 1.3250372409820557s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02126026153564453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00012230873107910156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 22.268651485443115s
Believability | Calculation of trust value for Bio2RDF::Interpro took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-interpro took 1121.0277214050293s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.14432048797607422s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.7372152805328369s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.62939453125e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-iproclass took 19.188796997070312s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.5837128162384033s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0007014274597167969s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 34.641883850097656s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2577366828918457s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 44.18438410758972s
Interoperability | New terms check for Bio2RDF::Irefindex took 43.423500537872314s
Versatility | Languages check for Bio2RDF::Irefindex took 60.27104878425598s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2608673572540283s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.1571943759918213s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.7936592102050781s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.36493515968322754s
Availability | RDF dump link check for Bio2RDF::Irefindex took 6.337293386459351s
License | MR license check for Bio2RDF::Irefindex took 0.585005521774292s
License | HR license check for Bio2RDF::Irefindex took 60.26188278198242s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.29708290100097656s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.442764043807983s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.6314952373504639s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.27841758728027344s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.3009803295135498s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2537386417388916s
Performance | Throughput check for Bio2RDF::Irefindex took 10.543370485305786s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 73.60094785690308s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.8674318790435791s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.39760804176330566s
Interlinking | skos check for Bio2RDF::Irefindex took 0.977536678314209s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3450040817260742s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2957725524902344s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5375146865844727s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5358560085296631s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 120.59226202964783s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 28.899041652679443s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.47926902770996094s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2756619453430176s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.28353452682495117s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 19.73121166229248s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.9061315059661865s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6961414813995361s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.5025880336761475s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 71.56649804115295s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.445726156234741s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 11.99265193939209s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.4076416492462158s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.60692262649536s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7021365165710449s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.7356290817260742s
Security | Sign check for Bio2RDF::Irefindex took 0.2791132926940918s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 11.523115396499634s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 1.4569835662841797s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.867813110351562e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 67.74401807785034s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 3.2901763916015625e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1163.1666672229767s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.7028622627258301s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.461143493652344e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-kegg took 6.37066388130188s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.25751280784606934s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.020586490631103516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.8994290828704834s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.16177988052368164s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2667872905731201s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.02031254768371582s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 2.86102294921875e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 9.393773794174194s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.5924687385559082s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006175041198730469s
Extra | Recovery of all triples for Bio2RDF::Lsr took 33.97702074050903s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.308283805847168s
Amount of data | Number of triples check for Bio2RDF::Lsr took 44.29984378814697s
Interoperability | New terms check for Bio2RDF::Lsr took 41.41964268684387s
Versatility | Languages check for Bio2RDF::Lsr took 60.250038862228394s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.27064967155456543s
Security | Check HTTPS for Bio2RDF::Lsr took 0.18036627769470215s
Interpretability | RDF structures check for Bio2RDF::Lsr took 1.0596816539764404s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.34563589096069336s
Availability | RDF dump link check for Bio2RDF::Lsr took 6.3491530418396s
License | MR license check for Bio2RDF::Lsr took 0.5716476440429688s
License | HR license check for Bio2RDF::Lsr took 60.24777626991272s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2858138084411621s
Understandability | Number of label check for Bio2RDF::Lsr took 10.910470724105835s
Understandability | URI regex check for Bio2RDF::Lsr took 0.6009101867675781s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.2685580253601074s
Verifiability | Authors check for Bio2RDF::Lsr took 0.2618391513824463s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.26274681091308594s
Performance | Throughput check for Bio2RDF::Lsr took 11.086323261260986s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 75.04166841506958s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.7493031024932861s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3932304382324219s
Interlinking | skos check for Bio2RDF::Lsr took 0.9909844398498535s
Interlinking | skos check for Bio2RDF::Lsr took 0.34564924240112305s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.2735936641693115s
Currency | Creation date check for Bio2RDF::Lsr took 0.5331575870513916s
Currency | Modification date check for Bio2RDF::Lsr took 0.549318790435791s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 119.97052836418152s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 58.510451555252075s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4472675323486328s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.3039054870605469s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.29521870613098145s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 18.348713636398315s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8975009918212891s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6595206260681152s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.4891061782836914s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 71.31335210800171s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.4666848182678223s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 11.890490293502808s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3741891384124756s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.64402413368225s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7233905792236328s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.7591023445129395s
Security | Sign check for Bio2RDF::Lsr took 0.27266907691955566s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 11.007675409317017s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 1.288588523864746s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020793676376342773s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 28.079853296279907s
Believability | Calculation of trust value for Bio2RDF::Lsr took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-lsr took 1153.0077121257782s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.588146448135376s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0006339550018310547s
Extra | Recovery of all triples for Bio2RDF::Mesh took 34.99995732307434s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2879109382629395s
Amount of data | Number of triples check for Bio2RDF::Mesh took 45.32439994812012s
Interoperability | New terms check for Bio2RDF::Mesh took 43.399765968322754s
Versatility | Languages check for Bio2RDF::Mesh took 60.255982637405396s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.2539083957672119s
Security | Check HTTPS for Bio2RDF::Mesh took 0.1581261157989502s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.9152853488922119s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.30986475944519043s
Availability | RDF dump link check for Bio2RDF::Mesh took 6.295313358306885s
License | MR license check for Bio2RDF::Mesh took 0.6731314659118652s
License | HR license check for Bio2RDF::Mesh took 60.26372194290161s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.30724024772644043s
Understandability | Number of label check for Bio2RDF::Mesh took 10.369081258773804s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5884511470794678s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2541663646697998s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2847135066986084s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2594153881072998s
Performance | Throughput check for Bio2RDF::Mesh took 10.693227291107178s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 73.84453773498535s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.7025933265686035s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.3539106845855713s
Interlinking | skos check for Bio2RDF::Mesh took 0.8287978172302246s
Interlinking | skos check for Bio2RDF::Mesh took 0.3729977607727051s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.28129029273986816s
Currency | Creation date check for Bio2RDF::Mesh took 0.5536038875579834s
Currency | Modification date check for Bio2RDF::Mesh took 0.5283241271972656s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 121.15914988517761s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 21.652047395706177s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.46916937828063965s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2996859550476074s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2871685028076172s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 18.1511070728302s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8920786380767822s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6641433238983154s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.5207934379577637s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 71.28008842468262s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.418911933898926s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 11.754078388214111s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3768093585968018s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.6020245552063s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7045516967773438s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 1.5509016513824463s
Security | Sign check for Bio2RDF::Mesh took 0.2976975440979004s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 11.69753122329712s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 1.0408742427825928s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 106.53689646720886s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-mesh took 1211.1669204235077s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.5986506938934326s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0005922317504882812s
Extra | Recovery of all triples for Bio2RDF::Mgi took 38.46850776672363s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2858874797821045s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.64850211143494s
Interoperability | New terms check for Bio2RDF::Mgi took 42.86403846740723s
Versatility | Languages check for Bio2RDF::Mgi took 60.24414920806885s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.27469682693481445s
Security | Check HTTPS for Bio2RDF::Mgi took 0.16361093521118164s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.9564704895019531s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.3526027202606201s
Availability | RDF dump link check for Bio2RDF::Mgi took 6.336035490036011s
License | MR license check for Bio2RDF::Mgi took 0.6869006156921387s
License | HR license check for Bio2RDF::Mgi took 60.250356674194336s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.25336456298828125s
Understandability | Number of label check for Bio2RDF::Mgi took 10.675250053405762s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5758280754089355s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.26862001419067383s
Verifiability | Authors check for Bio2RDF::Mgi took 0.27066612243652344s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2782752513885498s
Performance | Throughput check for Bio2RDF::Mgi took 11.074417352676392s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 76.03459024429321s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.2759273052215576s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.4340782165527344s
Interlinking | skos check for Bio2RDF::Mgi took 1.224496841430664s
Interlinking | skos check for Bio2RDF::Mgi took 0.3583052158355713s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2787957191467285s
Currency | Creation date check for Bio2RDF::Mgi took 0.5450143814086914s
Currency | Modification date check for Bio2RDF::Mgi took 0.5325241088867188s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 125.13309383392334s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 38.89851212501526s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.7259869575500488s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.26725101470947266s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.3112607002258301s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 17.473178148269653s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8980050086975098s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6672897338867188s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.5312111377716064s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 70.88999581336975s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4270927906036377s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 12.358615398406982s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3553366661071777s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.6265823841095s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7285480499267578s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.4916844367980957s
Security | Sign check for Bio2RDF::Mgi took 0.27663326263427734s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 22.56495976448059s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.8974056243896484s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.021973848342895508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.72747802734375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 103.1086061000824s
Believability | Calculation of trust value for Bio2RDF::Mgi took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-mgi took 1231.88987159729s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.5674188137054443s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006277561187744141s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 35.815999031066895s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2706208229064941s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.67339587211609s
Interoperability | New terms check for Bio2RDF::Ncbigene took 42.714802980422974s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.26763415336609s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.278454065322876s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.16936326026916504s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 1.1051223278045654s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.32372617721557617s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 6.2954699993133545s
License | MR license check for Bio2RDF::Ncbigene took 0.538689136505127s
License | HR license check for Bio2RDF::Ncbigene took 60.243884325027466s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.31975793838500977s
Understandability | Number of label check for Bio2RDF::Ncbigene took 10.141948461532593s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5595407485961914s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.26822328567504883s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.24979853630065918s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2715260982513428s
Performance | Throughput check for Bio2RDF::Ncbigene took 10.433106184005737s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 73.81841897964478s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.27746129035949707s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.4145231246948242s
Interlinking | skos check for Bio2RDF::Ncbigene took 1.1430213451385498s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3758430480957031s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.25232911109924316s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5679841041564941s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5234384536743164s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 120.42835211753845s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 109.54381680488586s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 1.2758204936981201s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2995753288269043s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.26546192169189453s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 17.425148248672485s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8939299583435059s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6629765033721924s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.4689497947692871s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 70.8307363986969s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.4116034507751465s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 12.553175926208496s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3499979972839355s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.5637104511261s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.710291862487793s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.44195079803466797s
Security | Sign check for Bio2RDF::Ncbigene took 0.2643160820007324s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 10.832605838775635s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.9382641315460205s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012612342834472656s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 21.686096668243408s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1208.0585916042328s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.6031126976013184s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006265640258789062s
Extra | Recovery of all triples for Bio2RDF::Ndc took 34.58608889579773s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2582495212554932s
Amount of data | Number of triples check for Bio2RDF::Ndc took 44.210493326187134s
Interoperability | New terms check for Bio2RDF::Ndc took 42.59626221656799s
Versatility | Languages check for Bio2RDF::Ndc took 60.268643856048584s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.26543307304382324s
Security | Check HTTPS for Bio2RDF::Ndc took 0.16814923286437988s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.9247629642486572s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.30727195739746094s
Availability | RDF dump link check for Bio2RDF::Ndc took 6.212890863418579s
License | MR license check for Bio2RDF::Ndc took 0.47058653831481934s
License | HR license check for Bio2RDF::Ndc took 60.24977421760559s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.26155686378479004s
Understandability | Number of label check for Bio2RDF::Ndc took 10.359071016311646s
Understandability | URI regex check for Bio2RDF::Ndc took 0.579920768737793s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2649571895599365s
Verifiability | Authors check for Bio2RDF::Ndc took 0.283933162689209s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.28131818771362305s
Performance | Throughput check for Bio2RDF::Ndc took 10.219944953918457s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 75.62169122695923s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.7265176773071289s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.36795735359191895s
Interlinking | skos check for Bio2RDF::Ndc took 0.9407038688659668s
Interlinking | skos check for Bio2RDF::Ndc took 0.3511326313018799s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.2509574890136719s
Currency | Creation date check for Bio2RDF::Ndc took 0.5727863311767578s
Currency | Modification date check for Bio2RDF::Ndc took 0.550673246383667s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 118.92851734161377s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 41.668657064437866s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.4115924835205078s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2823495864868164s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2842881679534912s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 19.229099988937378s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8915374279022217s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6890749931335449s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.3778717517852783s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 71.12280702590942s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4085474014282227s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 12.1154146194458s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.351621389389038s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.58115530014038s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7277712821960449s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.7324542999267578s
Security | Sign check for Bio2RDF::Ndc took 0.2925069332122803s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 12.25517988204956s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.47524428367614746s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 48.76466631889343s
Believability | Calculation of trust value for Bio2RDF::Ndc took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-ndc took 1158.8500046730042s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.2564058303833008s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-netpath took 4.634978532791138s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13896870613098145s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2662022113800049s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020799636840820312s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-nextprot took 3.301335573196411s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.5841155052185059s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0004737377166748047s
Extra | Recovery of all triples for Bio2RDF::Omim took 36.66692066192627s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.236494779586792s
Amount of data | Number of triples check for Bio2RDF::Omim took 44.258272647857666s
Interoperability | New terms check for Bio2RDF::Omim took 42.692168951034546s
Versatility | Languages check for Bio2RDF::Omim took 60.22954726219177s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2531874179840088s
Security | Check HTTPS for Bio2RDF::Omim took 0.15618658065795898s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.9599413871765137s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.3316497802734375s
Availability | RDF dump link check for Bio2RDF::Omim took 6.261749505996704s
License | MR license check for Bio2RDF::Omim took 0.5027000904083252s
License | HR license check for Bio2RDF::Omim took 60.238913774490356s
Amount of data | Number of property check for Bio2RDF::Omim took 0.3009645938873291s
Understandability | Number of label check for Bio2RDF::Omim took 11.120116472244263s
Understandability | URI regex check for Bio2RDF::Omim took 0.6114437580108643s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2586860656738281s
Verifiability | Authors check for Bio2RDF::Omim took 0.29131078720092773s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2508230209350586s
Performance | Throughput check for Bio2RDF::Omim took 10.738609075546265s
Amount of data | Check the number of entities for Bio2RDF::Omim took 76.59848308563232s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.6725642681121826s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.4148385524749756s
Interlinking | skos check for Bio2RDF::Omim took 1.0278904438018799s
Interlinking | skos check for Bio2RDF::Omim took 0.3658285140991211s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.2727494239807129s
Currency | Creation date check for Bio2RDF::Omim took 0.542738676071167s
Currency | Modification date check for Bio2RDF::Omim took 0.5595912933349609s
Rep.Conc. | URIs length for Bio2RDF::Omim took 121.53441667556763s
Interoperability | New vocabularies check for Bio2RDF::Omim took 31.579697608947754s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.46582984924316406s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2988765239715576s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2952244281768799s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 18.826289653778076s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8936750888824463s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.693535327911377s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.45478153228759766s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 71.1324634552002s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.480783700942993s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 11.60738205909729s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3622047901153564s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.62164878845215s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7057976722717285s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.7162165641784668s
Security | Sign check for Bio2RDF::Omim took 0.2801787853240967s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 10.461735248565674s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.972482442855835s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001266002655029297s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 109.86163210868835s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-omim took 1210.8554818630219s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 5.1021575927734375e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.7177739143371582s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.52587890625e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.000934600830078125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 5.4836273193359375e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 4.951453447341919s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.6026091575622559s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0007364749908447266s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 34.73116087913513s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.3306896686553955s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 44.987393379211426s
Interoperability | New terms check for Bio2RDF::Orphanet took 41.4894073009491s
Versatility | Languages check for Bio2RDF::Orphanet took 60.24247908592224s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.28139662742614746s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.17862796783447266s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.8649678230285645s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.35056519508361816s
Availability | RDF dump link check for Bio2RDF::Orphanet took 6.371304035186768s
License | MR license check for Bio2RDF::Orphanet took 0.5019299983978271s
License | HR license check for Bio2RDF::Orphanet took 60.24163866043091s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.2774066925048828s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.192127466201782s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5747475624084473s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.26296377182006836s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.28940844535827637s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.25426435470581055s
Performance | Throughput check for Bio2RDF::Orphanet took 10.824559688568115s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 74.17579078674316s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.7114882469177246s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.4062802791595459s
Interlinking | skos check for Bio2RDF::Orphanet took 0.8842184543609619s
Interlinking | skos check for Bio2RDF::Orphanet took 0.3333570957183838s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2545170783996582s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5260879993438721s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5484752655029297s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 123.63983368873596s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 107.75590515136719s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.42318177223205566s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.26541614532470703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2817201614379883s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 18.77197575569153s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.9034650325775146s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6635379791259766s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.4255847930908203s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 70.25936365127563s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 4.340537786483765s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 11.493420124053955s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3744049072265625s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.636937856674194s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7163114547729492s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.4153459072113037s
Security | Sign check for Bio2RDF::Orphanet took 0.28972482681274414s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 9.917248487472534s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.8330605030059814s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 7.915496826171875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 94.34911036491394s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1276.073225736618s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.1411876678466797s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.7047247886657715s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 11.668615341186523s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.6045539379119873s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0007007122039794922s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 36.09838271141052s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2727832794189453s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 44.58342170715332s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 42.020153284072876s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.25249123573303s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.28835439682006836s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.1476726531982422s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 1.1379890441894531s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.33185625076293945s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 6.412529945373535s
License | MR license check for Bio2RDF::Pharmgkb took 0.7838411331176758s
License | HR license check for Bio2RDF::Pharmgkb took 60.232054471969604s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2914743423461914s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.708697319030762s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.6008822917938232s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.25032949447631836s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.27878689765930176s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2528350353240967s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.063998937606812s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 77.11384677886963s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.9228720664978027s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.42664289474487305s
Interlinking | skos check for Bio2RDF::Pharmgkb took 1.0269105434417725s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.4103882312774658s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.26725006103515625s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.532463550567627s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5200698375701904s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 119.86279702186584s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 189.74002766609192s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.72916579246521s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.27255678176879883s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.27544355392456055s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 19.233933925628662s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.9038481712341309s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6662120819091797s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.41001105308532715s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 70.65260314941406s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.384979248046875s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 12.407213926315308s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3677592277526855s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.59959411621094s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.702193021774292s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4544665813446045s
Security | Sign check for Bio2RDF::Pharmgkb took 0.2617948055267334s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 11.828697443008423s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.5221099853515625s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.414817810058594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 126.47302770614624s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 2.002716064453125e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1393.431548833847s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.7054665088653564s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.652141332626343s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 7.152557373046875e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.2508277893066406s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.02097153663635254s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-pid took 2.914156436920166s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 7.2479248046875e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.2859029769897461s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.3796801567077637s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.6022446155548096s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0003643035888671875s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 36.11714172363281s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2860667705535889s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 43.76217174530029s
Interoperability | New terms check for Bio2RDF::Pubmed took 41.60901594161987s
Versatility | Languages check for Bio2RDF::Pubmed took 60.2418327331543s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.28039121627807617s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.15785622596740723s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 1.0692429542541504s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3470034599304199s
Availability | RDF dump link check for Bio2RDF::Pubmed took 6.2312657833099365s
License | MR license check for Bio2RDF::Pubmed took 0.5672407150268555s
License | HR license check for Bio2RDF::Pubmed took 60.23214316368103s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2774837017059326s
Understandability | Number of label check for Bio2RDF::Pubmed took 10.191138505935669s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6032421588897705s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2662513256072998s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.28966498374938965s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.2700042724609375s
Performance | Throughput check for Bio2RDF::Pubmed took 10.57939887046814s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 78.78363847732544s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 2.3057100772857666s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.398557186126709s
Interlinking | skos check for Bio2RDF::Pubmed took 0.9343099594116211s
Interlinking | skos check for Bio2RDF::Pubmed took 0.360152006149292s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.25786685943603516s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5560555458068848s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5139470100402832s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 121.66841125488281s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 106.2700207233429s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.432034969329834s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.30596923828125s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.27562689781188965s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 17.96489119529724s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8932051658630371s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6608798503875732s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.596503734588623s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 71.07725238800049s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.679290771484375s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 11.849549055099487s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3478889465332031s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.59811305999756s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7007758617401123s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.45166993141174316s
Security | Sign check for Bio2RDF::Pubmed took 0.2715334892272949s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 11.66317367553711s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.8502154350280762s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013756752014160156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 111.18928980827332s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1290.370789527893s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.7198998928070068s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 7.104873657226562e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-reactome took 5.1244423389434814s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.26788830757141113s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.2928924560546875e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.2894399166107178s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1454482078552246s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.26312971115112305s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.486343383789062e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-sabiork took 9.714595079421997s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.592024564743042s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005702972412109375s
Extra | Recovery of all triples for Bio2RDF::Sgd took 34.130372524261475s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2335906028747559s
Amount of data | Number of triples check for Bio2RDF::Sgd took 43.612812757492065s
Interoperability | New terms check for Bio2RDF::Sgd took 42.99395537376404s
Versatility | Languages check for Bio2RDF::Sgd took 60.24555540084839s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.28809595108032227s
Security | Check HTTPS for Bio2RDF::Sgd took 0.15643811225891113s
Interpretability | RDF structures check for Bio2RDF::Sgd took 1.1797232627868652s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.3571817874908447s
Availability | RDF dump link check for Bio2RDF::Sgd took 6.438336372375488s
License | MR license check for Bio2RDF::Sgd took 0.6106264591217041s
License | HR license check for Bio2RDF::Sgd took 60.23939371109009s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.29338908195495605s
Understandability | Number of label check for Bio2RDF::Sgd took 10.633388996124268s
Understandability | URI regex check for Bio2RDF::Sgd took 0.626694917678833s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2699553966522217s
Verifiability | Authors check for Bio2RDF::Sgd took 0.27837252616882324s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.26124095916748047s
Performance | Throughput check for Bio2RDF::Sgd took 10.418999671936035s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 74.90844559669495s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.7148168087005615s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.4373643398284912s
Interlinking | skos check for Bio2RDF::Sgd took 1.2232208251953125s
Interlinking | skos check for Bio2RDF::Sgd took 0.34911346435546875s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2721900939941406s
Currency | Creation date check for Bio2RDF::Sgd took 0.5305101871490479s
Currency | Modification date check for Bio2RDF::Sgd took 0.5170845985412598s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 122.22134494781494s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 76.8673448562622s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.39716482162475586s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2755413055419922s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.28265905380249023s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 17.889220476150513s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8998901844024658s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6671597957611084s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.4720926284790039s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 70.44276309013367s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4468564987182617s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 12.893571138381958s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3654730319976807s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.92759990692139s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7045028209686279s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.4507787227630615s
Security | Sign check for Bio2RDF::Sgd took 0.2635056972503662s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 11.600206851959229s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 1.092252492904663s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.02108621597290039s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0008358955383300781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011897087097167969s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 75.02523612976074s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.4543533325195312e-05s
INFO | --- Analysis for bio2rdf-sgd took 1219.7259538173676s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 6.651878356933594e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.287081241607666s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.409385681152344e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 3.1924145221710205s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.5933082103729248s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0005064010620117188s
Extra | Recovery of all triples for Bio2RDF::Sider took 33.83174419403076s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2809219360351562s
Amount of data | Number of triples check for Bio2RDF::Sider took 44.676782846450806s
Interoperability | New terms check for Bio2RDF::Sider took 43.6317572593689s
Versatility | Languages check for Bio2RDF::Sider took 60.27401161193848s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.2616899013519287s
Security | Check HTTPS for Bio2RDF::Sider took 0.15725088119506836s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.8412539958953857s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.359832763671875s
Availability | RDF dump link check for Bio2RDF::Sider took 6.36840295791626s
License | MR license check for Bio2RDF::Sider took 0.5459401607513428s
License | HR license check for Bio2RDF::Sider took 60.236496925354004s
Amount of data | Number of property check for Bio2RDF::Sider took 0.2791767120361328s
Understandability | Number of label check for Bio2RDF::Sider took 10.30479383468628s
Understandability | URI regex check for Bio2RDF::Sider took 0.5913493633270264s
Understandability | Vocabs check for Bio2RDF::Sider took 0.24949169158935547s
Verifiability | Authors check for Bio2RDF::Sider took 0.2836751937866211s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2753129005432129s
Performance | Throughput check for Bio2RDF::Sider took 11.440489053726196s
Amount of data | Check the number of entities for Bio2RDF::Sider took 75.73103833198547s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.9099490642547607s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3760807514190674s
Interlinking | skos check for Bio2RDF::Sider took 0.9947926998138428s
Interlinking | skos check for Bio2RDF::Sider took 0.38338565826416016s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2438669204711914s
Currency | Creation date check for Bio2RDF::Sider took 0.5324020385742188s
Currency | Modification date check for Bio2RDF::Sider took 0.5257947444915771s
Rep.Conc. | URIs length for Bio2RDF::Sider took 123.48816514015198s
Interoperability | New vocabularies check for Bio2RDF::Sider took 52.027669191360474s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.4058971405029297s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.2859327793121338s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2970283031463623s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 18.67491602897644s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.908231258392334s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6922323703765869s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.4192323684692383s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 70.721519947052s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.4344546794891357s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 12.610266923904419s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.422142505645752s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.62419891357422s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7036445140838623s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.8053491115570068s
Security | Sign check for Bio2RDF::Sider took 0.28972935676574707s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 12.713419437408447s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.581047534942627s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020971298217773438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 22.467010498046875s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-sider took 1149.008555650711s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 5.53131103515625e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.3118560314178467s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020740032196044922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.24249267578125e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-spike took 4.693572282791138s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.291534423828125e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2779092788696289s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020747661590576172s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.076957702636719e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-taxon took 3.5389246940612793s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.6174383163452148s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0003838539123535156s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 35.789549827575684s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2672665119171143s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 44.47416019439697s
Interoperability | New terms check for Bio2RDF::Taxonomy took 45.52769088745117s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.254785776138306s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2655816078186035s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.1469404697418213s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.886615514755249s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.35892271995544434s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 6.384670972824097s
License | MR license check for Bio2RDF::Taxonomy took 0.841832160949707s
License | HR license check for Bio2RDF::Taxonomy took 60.25878429412842s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.281036376953125s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.679640054702759s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6061985492706299s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2559478282928467s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.2728261947631836s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2682642936706543s
Performance | Throughput check for Bio2RDF::Taxonomy took 10.825573444366455s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 74.80810594558716s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.2518472671508789s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.40385985374450684s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.942190408706665s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.38440656661987305s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.26783227920532227s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5333948135375977s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5527737140655518s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 120.54614758491516s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 68.79903745651245s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 1.5125539302825928s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.27170228958129883s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2958221435546875s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 18.549883365631104s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8936283588409424s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6721072196960449s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.4285902976989746s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 70.36972236633301s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.457181930541992s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 11.841356992721558s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.4002854824066162s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.62439775466919s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7087380886077881s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.43611907958984375s
Security | Sign check for Bio2RDF::Taxonomy took 0.28128528594970703s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 10.96943974494934s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.9032034873962402s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010228157043457031s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 22.995411157608032s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1162.8628883361816s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.14753341674804688s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 1.267509937286377s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 19.85377597808838s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.5903499126434326s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0004067420959472656s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 34.75678539276123s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2566807270050049s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 43.75390553474426s
Interoperability | New terms check for Bio2RDF::Wormbase took 44.591572761535645s
Versatility | Languages check for Bio2RDF::Wormbase took 60.24576687812805s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.2906649112701416s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.1462390422821045s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.9951753616333008s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3376638889312744s
Availability | RDF dump link check for Bio2RDF::Wormbase took 6.3216636180877686s
License | MR license check for Bio2RDF::Wormbase took 0.5476362705230713s
License | HR license check for Bio2RDF::Wormbase took 60.250349283218384s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.26561522483825684s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.258471727371216s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6017851829528809s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.26460838317871094s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2781486511230469s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.259291410446167s
Performance | Throughput check for Bio2RDF::Wormbase took 11.04638934135437s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 74.62878394126892s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.2903571128845215s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.4009981155395508s
Interlinking | skos check for Bio2RDF::Wormbase took 0.9657771587371826s
Interlinking | skos check for Bio2RDF::Wormbase took 0.3502016067504883s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.28472471237182617s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5342121124267578s
Currency | Modification date check for Bio2RDF::Wormbase took 0.525801420211792s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 120.19602751731873s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 77.20436596870422s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.7213926315307617s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.27735161781311035s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.28488779067993164s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 20.398771286010742s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8893640041351318s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.7179794311523438s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.39362144470214844s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 70.57827758789062s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.4176244735717773s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 12.194149494171143s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3620383739471436s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.62601089477539s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7032480239868164s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.4163508415222168s
Security | Sign check for Bio2RDF::Wormbase took 0.26825761795043945s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 10.952922582626343s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 1.3623945713043213s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.606910705566406e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 171.2034330368042s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1321.0968120098114s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 5.364418029785156e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.24725723266601562s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.02077937126159668s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.33514404296875e-05s
Believability | Calculation of trust value for Biografías y Vidas took 8.344650268554688e-06s
INFO | --- Analysis for biografiasyvidas took 3.1622729301452637s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.28652310371398926s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.2592735290527344s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 9.632110595703125e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 5.4836273193359375e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.5942513942718506s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0001850128173828125s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.23257803916931152s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020328283309936523s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.8848648071289062e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for biolit took 3.287961959838867s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.696846008300781e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0003192424774169922s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.24942898750305176s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.00543212890625e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 6.67572021484375e-06s
INFO | --- Analysis for biolod-pdb took 7.814258337020874s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.5693824291229248s
Availability | VoID file availability check for BioModels RDF took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2831900119781494s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.600120544433594e-05s
Believability | Calculation of trust value for BioModels RDF took 8.344650268554688e-06s
INFO | --- Analysis for biomodels-rdf took 3.563049793243408s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.874783992767334s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0013082027435302734s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.26983022689819336s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.123283386230469e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.3909759521484375e-06s
INFO | --- Analysis for Biop took 7.495283365249634s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.315376281738281e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.26825451850891113s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020734786987304688s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0009431838989257812s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.076957702636719e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.867813110351562e-06s
INFO | --- Analysis for Bioportal took 2.40046763420105s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 5.125999450683594e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2564425468444824s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006411075592041016s
Believability | Calculation of trust value for Amphibian gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-aao took 3.163831949234009s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.458427429199219e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0003457069396972656s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2627127170562744s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02067875862121582s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00029540061950683594s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-aba took 2.5754599571228027s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.25112295150756836s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020802974700927734s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015215873718261719s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-acgt took 2.6088039875030518s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.458427429199219e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.25675439834594727s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.001069784164428711s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0004124641418457031s
Believability | Calculation of trust value for Animal natural history and life history took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-adw took 2.601231813430786s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.2652924060821533s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00047135353088378906s
Believability | Calculation of trust value for Anatomical Entity Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-aeo took 2.6112375259399414s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 5.555152893066406e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0012743473052978516s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.23970866203308105s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02197122573852539s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0010883808135986328s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-aero took 2.4499058723449707s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.506111145019531e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2912631034851074s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020962238311767578s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004630088806152344s
Believability | Calculation of trust value for AI/RHEUM took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-air took 2.6665802001953125s
Availability | SPARQL endpoint availability check for Amino Acid took 5.841255187988281e-05s
Availability | VoID file availability check for Amino Acid took 0.00041937828063964844s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.24408555030822754s
Reputation | Calculation of the PageRank for Amino Acid took 0.020757436752319336s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0003190040588378906s
Believability | Calculation of trust value for Amino Acid took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.6188931465148926s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2622048854827881s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.021033763885498047s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0003161430358886719s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-apo took 2.527280569076538s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.4345855712890625e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0011737346649169922s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2619307041168213s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00024127960205078125s
Believability | Calculation of trust value for African Traditional Medicine took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-atmo took 2.5250802040100098s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.172325134277344e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.26258349418640137s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.021370410919189453s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.298324584960938e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ato took 2.5718541145324707s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0009665489196777344s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.26305389404296875s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02085733413696289s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0009694099426269531s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0014324188232421875s
Believability | Calculation of trust value for BioAssay Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bao took 2.586669683456421s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.57763671875e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2705988883972168s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020926475524902344s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0004398822784423828s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.5802555084228516s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0011320114135742188s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.24620556831359863s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.00032258033752441406s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bcgo took 2.587517499923706s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.2714579105377197s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020804166793823242s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014040470123291016s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-bdo took 2.6053566932678223s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2699868679046631s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004999637603759766s
Believability | Calculation of trust value for Basic Formal Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bfo took 2.5748767852783203s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.38690185546875e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.25040721893310547s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.00072479248046875s
Believability | Calculation of trust value for Bleeding History Phenotype took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bho took 2.5298843383789062s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.673004150390625e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.25550007820129395s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004513263702392578s
Believability | Calculation of trust value for Bilateria anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bila took 2.475527048110962s
Availability | SPARQL endpoint availability check for BIRNLex took 4.410743713378906e-05s
Availability | VoID file availability check for BIRNLex took 0.00034165382385253906s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.26354432106018066s
Reputation | Calculation of the PageRank for BIRNLex took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014908313751220703s
Believability | Calculation of trust value for BIRNLex took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-birnlex took 2.6326546669006348s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2533907890319824s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007839202880859375s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.633805513381958s
Availability | SPARQL endpoint availability check for BioPAX took 4.506111145019531e-05s
Availability | VoID file availability check for BioPAX took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2652251720428467s
Reputation | Calculation of the PageRank for BioPAX took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0008542537689208984s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.0001087188720703125s
Believability | Calculation of trust value for BioPAX took 1.52587890625e-05s
INFO | --- Analysis for bioportal-bp took 2.558519124984741s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 7.557868957519531e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2617621421813965s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.02072596549987793s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00035572052001953125s
Believability | Calculation of trust value for Biomedical Resource Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.556572198867798s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.24294352531433105s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0008196830749511719s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00024199485778808594s
Believability | Calculation of trust value for Spatial Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bspo took 2.505312204360962s
Availability | SPARQL endpoint availability check for BioTop took 4.410743713378906e-05s
Availability | VoID file availability check for BioTop took 0.0004093647003173828s
Completeness | Calculation of interlinking completeness for BioTop took 0.24548816680908203s
Reputation | Calculation of the PageRank for BioTop took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006442070007324219s
Believability | Calculation of trust value for BioTop took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bt took 2.4561688899993896s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.363059997558594e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.24496960639953613s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008871555328369141s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bto took 2.4574365615844727s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0004036426544189453s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.31366896629333496s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018482208251953125s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-canco took 3.0531258583068848s
Availability | SPARQL endpoint availability check for CAO took 4.410743713378906e-05s
Availability | VoID file availability check for CAO took 0.0003974437713623047s
Completeness | Calculation of interlinking completeness for CAO took 0.274017333984375s
Reputation | Calculation of the PageRank for CAO took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for CAO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005767345428466797s
Believability | Calculation of trust value for CAO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cao took 2.5235989093780518s
Availability | SPARQL endpoint availability check for CareLex took 4.458427429199219e-05s
Availability | VoID file availability check for CareLex took 0.0004107952117919922s
Completeness | Calculation of interlinking completeness for CareLex took 0.2485065460205078s
Reputation | Calculation of the PageRank for CareLex took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.078315734863281e-05s
Believability | Calculation of trust value for CareLex took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-carelex took 2.5506961345672607s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00034356117248535156s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2393205165863037s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008106231689453125s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cco took 2.5441901683807373s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.25863003730773926s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020292282104492188s
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.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002529621124267578s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cdao took 2.519686698913574s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.482269287109375e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2557401657104492s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008137226104736328s
Believability | Calculation of trust value for Chemical entities of biological interest took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-chebi took 2.538311243057251s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.3392181396484375e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.2871265411376953s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002541542053222656s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.507499933242798s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.2483844757080078s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007567405700683594s
Believability | Calculation of trust value for Chemical Information Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cheminf took 2.537569999694824s
Availability | SPARQL endpoint availability check for Cell type took 4.482269287109375e-05s
Availability | VoID file availability check for Cell type took 0.0007979869842529297s
Completeness | Calculation of interlinking completeness for Cell type took 0.25658345222473145s
Reputation | Calculation of the PageRank for Cell type took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00037169456481933594s
Believability | Calculation of trust value for Cell type took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cl took 2.4684863090515137s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.25744104385375977s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008127689361572266s
Believability | Calculation of trust value for Cell Line Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-clo took 2.5353832244873047s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 6.67572021484375e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2576291561126709s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017142295837402344s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cmo took 2.4794821739196777s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.2697744369506836s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002028942108154297s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cno took 2.5442354679107666s
Availability | SPARQL endpoint availability check for Wheat trait took 4.38690185546875e-05s
Availability | VoID file availability check for Wheat trait took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.25429201126098633s
Reputation | Calculation of the PageRank for Wheat trait took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.364418029785156e-05s
Believability | Calculation of trust value for Wheat trait took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.517949104309082s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.6253204345703125e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.24579262733459473s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020259618759155273s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003306865692138672s
Believability | Calculation of trust value for Cognitive Atlas took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-cogat took 2.5481526851654053s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.258512020111084s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020483016967773438s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007305145263671875s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-cogpo took 2.4723968505859375s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.839897155761719e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.23694300651550293s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004127025604248047s
Believability | Calculation of trust value for Current Procedural Terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cpt took 2.513075351715088s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.482269287109375e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0004088878631591797s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.2793443202972412s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.001745462417602539s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-csp took 2.932318687438965s
Availability | SPARQL endpoint availability check for COSTART took 4.38690185546875e-05s
Availability | VoID file availability check for COSTART took 0.00033593177795410156s
Completeness | Calculation of interlinking completeness for COSTART took 0.24978208541870117s
Reputation | Calculation of the PageRank for COSTART took 0.02051401138305664s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009658336639404297s
Believability | Calculation of trust value for COSTART took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cst took 2.4950215816497803s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.315376281738281e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0003292560577392578s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.24978876113891602s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004942417144775391s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ctcae took 2.472564220428467s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.2438507080078125e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.24623775482177734s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004439353942871094s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ctx took 2.4742014408111572s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.458427429199219e-05s
Availability | VoID file availability check for Dendritic cell took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.24650311470031738s
Reputation | Calculation of the PageRank for Dendritic cell took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0003039836883544922s
Believability | Calculation of trust value for Dendritic cell took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.5559160709381104s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.00040435791015625s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2470109462738037s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.678436279296875e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ddanat took 2.5178465843200684s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2604529857635498s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020883560180664062s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009322166442871094s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ddi took 2.5493834018707275s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0003345012664794922s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.23735952377319336s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020813941955566406s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.273124694824219e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.4839463233947754s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2633492946624756s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00016355514526367188s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.5639026165008545s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.25653982162475586s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006313323974609375s
Believability | Calculation of trust value for Human disease ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-doid took 2.674583911895752s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.25104427337646484s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.021596908569335938s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008268356323242188s
Believability | Calculation of trust value for Electrocardiography Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ecg took 2.6040146350860596s
Availability | SPARQL endpoint availability check for Evidence codes took 4.410743713378906e-05s
Availability | VoID file availability check for Evidence codes took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.25000691413879395s
Reputation | Calculation of the PageRank for Evidence codes took 0.020807504653930664s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.2901763916015625e-05s
Believability | Calculation of trust value for Evidence codes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-eco took 2.4964404106140137s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3271512985229492s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017321109771728516s
Believability | Calculation of trust value for Experimental Factor Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-efo took 2.9584712982177734s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.57763671875e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.29537320137023926s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011818408966064453s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ehda took 2.6022627353668213s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 7.891654968261719e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0010981559753417969s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.25402235984802246s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02048182487487793s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007519721984863281s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.573823928833008s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.410743713378906e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.24783563613891602s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005147457122802734s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.63659930229187s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.38690185546875e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0010824203491210938s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2808196544647217s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.765655517578125e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-emap took 2.572777032852173s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Environment Ontology took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.24601244926452637s
Reputation | Calculation of the PageRank for Environment Ontology took 0.021068572998046875s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00041675567626953125s
Believability | Calculation of trust value for Environment Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-envo took 2.5136470794677734s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.506111145019531e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2522425651550293s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0008075237274169922s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00034356117248535156s
Believability | Calculation of trust value for Plant environmental conditions took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-eo took 2.561929941177368s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.25040507316589355s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012154579162597656s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ep took 2.5756454467773438s
Availability | SPARQL endpoint availability check for Epilepsy took 4.3392181396484375e-05s
Availability | VoID file availability check for Epilepsy took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2624092102050781s
Reputation | Calculation of the PageRank for Epilepsy took 0.021002531051635742s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0008676052093505859s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.000152587890625s
Believability | Calculation of trust value for Epilepsy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-epileponto took 2.5174522399902344s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 7.033348083496094e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.27588534355163574s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020789384841918945s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011527538299560547s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ero took 2.6879115104675293s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.410743713378906e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2768268585205078s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.02031421661376953s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011394023895263672s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ev took 2.553370714187622s
Availability | SPARQL endpoint availability check for ExO took 4.4345855712890625e-05s
Availability | VoID file availability check for ExO took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for ExO took 0.25902605056762695s
Reputation | Calculation of the PageRank for ExO took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for ExO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00023889541625976562s
Believability | Calculation of trust value for ExO took 1.5020370483398438e-05s
INFO | --- Analysis for bioportal-exo took 2.543508529663086s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.26378607749938965s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00010800361633300781s
Believability | Calculation of trust value for Fungal gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fao took 2.4469027519226074s
Availability | SPARQL endpoint availability check for Biological imaging methods took 8.58306884765625e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.257282018661499s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00018715858459472656s
Believability | Calculation of trust value for Biological imaging methods took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbbi took 2.5418143272399902s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2516307830810547s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02085113525390625s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006666183471679688s
Believability | Calculation of trust value for Drosophila gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbbt took 2.553544044494629s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.57763671875e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.24773240089416504s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00042939186096191406s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbcv took 2.5475966930389404s
Availability | SPARQL endpoint availability check for Drosophila development took 5.698204040527344e-05s
Availability | VoID file availability check for Drosophila development took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2664632797241211s
Reputation | Calculation of the PageRank for Drosophila development took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.8160552978515625e-05s
Believability | Calculation of trust value for Drosophila development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbdv took 2.562537670135498s
Availability | SPARQL endpoint availability check for Fly taxonomy took 8.106231689453125e-05s
Availability | VoID file availability check for Fly taxonomy took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.24752163887023926s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.00036144256591796875s
Believability | Calculation of trust value for Fly taxonomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fbsp took 2.6236276626586914s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.887580871582031e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2497544288635254s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0008068084716796875s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00026535987854003906s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.6290128231048584s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 5.745887756347656e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2505073547363281s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004107952117919922s
Believability | Calculation of trust value for Family Health History Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-fhho took 2.5301120281219482s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.24190688133239746s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02095508575439453s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0008366107940673828s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0011107921600341797s
Believability | Calculation of trust value for Influenza Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-flu took 2.541818380355835s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.5299530029296875e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2641901969909668s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020315170288085938s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.270408630371094e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fma took 2.5900542736053467s
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.0005843639373779297s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2391035556793213s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001323223114013672s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fypo took 2.5928142070770264s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 5.0067901611328125e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.268798828125s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.021343231201171875s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.369850158691406e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-geospecies took 2.623291492462158s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2524423599243164s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00015735626220703125s
Believability | Calculation of trust value for General Formal Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-gfo took 2.5276079177856445s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.2438507080078125e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.26581788063049316s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005984306335449219s
Believability | Calculation of trust value for General Formal Ontology: Biology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.5931081771850586s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.553794860839844e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.27094292640686035s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008792877197265625s
Believability | Calculation of trust value for Gene Ontology Extension took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.6456854343414307s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.26958274841308594s
Reputation | Calculation of the PageRank for Gene Ontology took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008487701416015625s
Believability | Calculation of trust value for Gene Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.657393217086792s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.38690185546875e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.2532765865325928s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 2.8371810913085938e-05s
Believability | Calculation of trust value for Cereal Plant Development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gro took 2.5188474655151367s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.482269287109375e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.28546977043151855s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.02023148536682129s
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.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004429817199707031s
Believability | Calculation of trust value for Cereal plant gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.603577136993408s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.29128193855285645s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007429122924804688s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.663238525390625s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.25072669982910156s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005524158477783203s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-hao took 2.5692617893218994s
Availability | SPARQL endpoint availability check for HCPCS took 4.410743713378906e-05s
Availability | VoID file availability check for HCPCS took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for HCPCS took 0.27858495712280273s
Reputation | Calculation of the PageRank for HCPCS took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002295970916748047s
Believability | Calculation of trust value for HCPCS took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.589303493499756s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.38690185546875e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.24997210502624512s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.001283407211303711s
Believability | Calculation of trust value for Health Level Seven took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hl7 took 2.590428590774536s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.506111145019531e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2784864902496338s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.021787166595458984s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00036263465881347656s
Believability | Calculation of trust value for HEALTH_INDICATORS took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.5865986347198486s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 7.414817810058594e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2770571708679199s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 2.8133392333984375e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hom took 2.575892448425293s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.267692565917969e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.26828742027282715s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 2.9802322387695312e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.583963632583618s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.887580871582031e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.253542423248291s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006415843963623047s
Believability | Calculation of trust value for Human Phenotype Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.5011281967163086s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.270188570022583s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020312070846557617s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.001020193099975586s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hpio took 2.583678722381592s
Availability | SPARQL endpoint availability check for HUGO took 6.604194641113281e-05s
Availability | VoID file availability check for HUGO took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for HUGO took 0.2553379535675049s
Reputation | Calculation of the PageRank for HUGO took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for HUGO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HUGO took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.772445678710938e-05s
Believability | Calculation of trust value for HUGO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hugo took 2.5950658321380615s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0003452301025390625s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.2529466152191162s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006365776062011719s
Believability | Calculation of trust value for Information Artifact Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-iao took 2.557839870452881s
Availability | SPARQL endpoint availability check for ICD10 took 9.679794311523438e-05s
Availability | VoID file availability check for ICD10 took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for ICD10 took 0.24630045890808105s
Reputation | Calculation of the PageRank for ICD10 took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008027553558349609s
Believability | Calculation of trust value for ICD10 took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-icd10 took 2.610891819000244s
Availability | SPARQL endpoint availability check for ICD10CM took 4.410743713378906e-05s
Availability | VoID file availability check for ICD10CM took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.2743346691131592s
Reputation | Calculation of the PageRank for ICD10CM took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006105899810791016s
Believability | Calculation of trust value for ICD10CM took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.620490789413452s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.363059997558594e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.25801753997802734s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015473365783691406s
Believability | Calculation of trust value for ICD-10-PCS took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.555229425430298s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.5299530029296875e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.27647995948791504s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006403923034667969s
Believability | Calculation of trust value for International Classification of Diseases took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.644895553588867s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 5.5789947509765625e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.27014946937561035s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.02025461196899414s
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.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004458427429199219s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.6278278827667236s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.410743713378906e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2708759307861328s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012443065643310547s
Believability | Calculation of trust value for International Classification for Nursing Practice took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-icnp took 2.6097354888916016s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.792213439941406e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.26822662353515625s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00045943260192871094s
Believability | Calculation of trust value for International Classification of Primary Care took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icpc took 2.5073094367980957s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.482269287109375e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2756075859069824s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008516311645507812s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.5799765586853027s
Availability | SPARQL endpoint availability check for ICPS Network took 4.5299530029296875e-05s
Availability | VoID file availability check for ICPS Network took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.27187442779541016s
Reputation | Calculation of the PageRank for ICPS Network took 0.022505521774291992s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0012254714965820312s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0003216266632080078s
Believability | Calculation of trust value for ICPS Network took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icps took 2.583728551864624s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.25763630867004395s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008800029754638672s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ido took 2.556025266647339s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.27130818367004395s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011725425720214844s
Believability | Calculation of trust value for Brucellosis Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-idobru took 2.584737777709961s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.254683256149292s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.001325368881225586s
Believability | Calculation of trust value for Malaria Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-idomal took 2.545551061630249s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 7.939338684082031e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2658843994140625s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02165365219116211s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0008189678192138672s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.000347137451171875s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-iev took 2.5481698513031006s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.3392181396484375e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.26932311058044434s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.0001494884490966797s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-imgt took 2.635974884033203s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.6253204345703125e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2674882411956787s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005466938018798828s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-imr took 2.564889907836914s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 5.555152893066406e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.25672125816345215s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008480548858642578s
Believability | Calculation of trust value for Interaction Network Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ino took 2.526552200317383s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.553794860839844e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.25951504707336426s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 2.8848648071289062e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.5566465854644775s
Availability | SPARQL endpoint availability check for IxnO took 4.4345855712890625e-05s
Availability | VoID file availability check for IxnO took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for IxnO took 0.2583737373352051s
Reputation | Calculation of the PageRank for IxnO took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for IxnO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0008256435394287109s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0002148151397705078s
Believability | Calculation of trust value for IxnO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ixno took 2.6802098751068115s
Availability | SPARQL endpoint availability check for SysMO-JERM took 5.245208740234375e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.25417423248291016s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.02025437355041504s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003807544708251953s
Believability | Calculation of trust value for SysMO-JERM took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-jerm took 2.5221073627471924s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.27001094818115234s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020168542861938477s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-kisao took 2.596040725708008s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 5.841255187988281e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.25681042671203613s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00019884109497070312s
Believability | Calculation of trust value for Loggerhead nesting took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-lhn took 2.6074466705322266s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.25649285316467285s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 6.318092346191406e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00021767616271972656s
Believability | Calculation of trust value for Lipid Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-lipro took 2.6129965782165527s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.792213439941406e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3211944103240967s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.02097487449645996s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018422603607177734s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-lnc took 3.0903220176696777s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2801816463470459s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.000675201416015625s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ma took 2.5286715030670166s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.553794860839844e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.24560976028442383s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002067089080810547s
Believability | Calculation of trust value for Multiple alignment took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mao took 2.605308771133423s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.410743713378906e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.26874852180480957s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006921291351318359s
Believability | Calculation of trust value for Minimal anatomical terminology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mat took 2.565131187438965s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.363059997558594e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.2766735553741455s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020731449127197266s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0009081363677978516s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004608631134033203s
Believability | Calculation of trust value for Breast tissue cell lines took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.6281423568725586s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Cell line ontology took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.23991799354553223s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02070331573486328s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007886886596679688s
Believability | Calculation of trust value for Cell line ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mccl took 2.5629043579101562s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26517605781555176s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014035701751708984s
Believability | Calculation of trust value for Cell line ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.5422775745391846s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.482269287109375e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.26397204399108887s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002446174621582031s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mcv took 2.5725889205932617s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.9591064453125e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2659916877746582s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02078080177307129s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001766681671142578s
Believability | Calculation of trust value for Master Drug Data Base took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mddb took 2.5549864768981934s
Availability | SPARQL endpoint availability check for MedDRA took 4.4345855712890625e-05s
Availability | VoID file availability check for MedDRA took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2929348945617676s
Reputation | Calculation of the PageRank for MedDRA took 0.02106022834777832s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0009644031524658203s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0013012886047363281s
Believability | Calculation of trust value for MedDRA took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mdr took 2.565289258956909s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 7.557868957519531e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.25631022453308105s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008876323699951172s
Believability | Calculation of trust value for MedlinePlus Health Topics took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.6467370986938477s
Availability | SPARQL endpoint availability check for MeGO took 4.3392181396484375e-05s
Availability | VoID file availability check for MeGO took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for MeGO took 0.2813246250152588s
Reputation | Calculation of the PageRank for MeGO took 0.021575450897216797s
Interlinking | Calculation of Degree of Connection for MeGO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MeGO took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001575946807861328s
Believability | Calculation of trust value for MeGO took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-mego took 2.6330478191375732s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.649162292480469e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3135719299316406s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.021140575408935547s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018811225891113281s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.0218844413757324s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.76837158203125e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2848818302154541s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006396770477294922s
Believability | Calculation of trust value for Mental Functioning Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mf took 2.799862861633301s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.482269287109375e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2907073497772217s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0006101131439208984s
Believability | Calculation of trust value for Medaka fish anatomy and development took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-mfo took 2.622258186340332s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2716977596282959s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.021625757217407227s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0010535717010498047s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0009379386901855469s
Believability | Calculation of trust value for Emotion Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mfoem took 2.540605068206787s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.24924945831298828s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.000110626220703125s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mhc took 2.5733792781829834s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.2438507080078125e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2682480812072754s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.021486282348632812s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0007042884826660156s
Believability | Calculation of trust value for Protein-protein interaction took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mi took 2.6193413734436035s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.506111145019531e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2673153877258301s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0008211135864257812s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007588863372802734s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-miro took 2.612483024597168s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 5.1021575927734375e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.28139591217041016s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001423358917236328s
Believability | Calculation of trust value for Measurement Method Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mmo took 2.653900384902954s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.24648332595825195s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021686077117919922s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003924369812011719s
Believability | Calculation of trust value for MGED Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-mo took 2.565173864364624s
Availability | SPARQL endpoint availability check for Protein modification took 4.935264587402344e-05s
Availability | VoID file availability check for Protein modification took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2659621238708496s
Reputation | Calculation of the PageRank for Protein modification took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002238750457763672s
Believability | Calculation of trust value for Protein modification took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mod took 2.544542074203491s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.5299530029296875e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.2680182456970215s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02088642120361328s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006649494171142578s
Believability | Calculation of trust value for Mammalian phenotype took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mp took 2.548846960067749s
Availability | SPARQL endpoint availability check for Mouse pathology took 5.245208740234375e-05s
Availability | VoID file availability check for Mouse pathology took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.25716662406921387s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020999431610107422s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004935264587402344s
Believability | Calculation of trust value for Mouse pathology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mpath took 2.577176332473755s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.4345855712890625e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.26958680152893066s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0004088878631591797s
Believability | Calculation of trust value for Mass spectrometry took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ms took 2.5266635417938232s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 5.173683166503906e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.28592801094055176s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0019207000732421875s
Believability | Calculation of trust value for Medical Subject Headings took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-msh took 3.0246951580047607s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.410743713378906e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2627418041229248s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020865678787231445s
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.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00017452239990234375s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mthch took 2.58831787109375s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.26790642738342285s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008037090301513672s
Believability | Calculation of trust value for Natural Products Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-natpro took 2.5563464164733887s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 5.9604644775390625e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.268390417098999s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02090311050415039s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008130073547363281s
Believability | Calculation of trust value for NCBI organismal classification took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.59946870803833s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.482269287109375e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.33098816871643066s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02091670036315918s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0020322799682617188s
Believability | Calculation of trust value for NCI Thesaurus took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ncit took 3.0307631492614746s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.38690185546875e-05s
Availability | VoID file availability check for National Drug Data File took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.2638542652130127s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006115436553955078s
Believability | Calculation of trust value for National Drug Data File took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nddf took 2.5744540691375732s
Availability | SPARQL endpoint availability check for National Drug File took 4.482269287109375e-05s
Availability | VoID file availability check for National Drug File took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2478923797607422s
Reputation | Calculation of the PageRank for National Drug File took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for National Drug File took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0013294219970703125s
Believability | Calculation of trust value for National Drug File took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.607116222381592s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.458427429199219e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.25504517555236816s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011606216430664062s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.5562148094177246s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2524566650390625s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006916522979736328s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-neomark took 2.5053505897521973s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.26854419708251953s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0009069442749023438s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00014734268188476562s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.5244855880737305s
Availability | SPARQL endpoint availability check for NIFSTD took 6.127357482910156e-05s
Availability | VoID file availability check for NIFSTD took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.327925443649292s
Reputation | Calculation of the PageRank for NIFSTD took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.00189971923828125s
Believability | Calculation of trust value for NIFSTD took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif took 3.0348310470581055s
Availability | SPARQL endpoint availability check for NIF Cell took 4.267692565917969e-05s
Availability | VoID file availability check for NIF Cell took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2694053649902344s
Reputation | Calculation of the PageRank for NIF Cell took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for NIF Cell took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013246536254882812s
Believability | Calculation of trust value for NIF Cell took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.5767223834991455s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.506111145019531e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.26820874214172363s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0013916492462158203s
Believability | Calculation of trust value for NIF Dysfunction took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.5799307823181152s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2567005157470703s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0009002685546875s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0006115436553955078s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nigo took 2.5714271068573s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.267692565917969e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2657346725463867s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005514621734619141s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nmr took 2.550045967102051s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.25182223320007324s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020741939544677734s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011134147644042969s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.5945637226104736s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.2498455047607422s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011630058288574219s
Believability | Calculation of trust value for NanoParticle Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-npo took 2.51936411857605s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 5.4836273193359375e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.27335309982299805s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007193088531494141s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-oae took 2.6587021350860596s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.6253204345703125e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.24669575691223145s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.001458883285522461s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-obi took 2.541529417037964s
Availability | SPARQL endpoint availability check for OBOE took 4.458427429199219e-05s
Availability | VoID file availability check for OBOE took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for OBOE took 0.24332976341247559s
Reputation | Calculation of the PageRank for OBOE took 0.02050161361694336s
Interlinking | Calculation of Degree of Connection for OBOE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.0001087188720703125s
Believability | Calculation of trust value for OBOE took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-oboe took 2.6489133834838867s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.649162292480469e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2993607521057129s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007822513580322266s
Believability | Calculation of trust value for OBOE SBC took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.6515135765075684s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2695887088775635s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0006163120269775391s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ocre took 2.6488165855407715s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.458427429199219e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.27921557426452637s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020406007766723633s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008571147918701172s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-odgi took 2.6028642654418945s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 7.152557373046875e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.00040793418884277344s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2588033676147461s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008780956268310547s
Believability | Calculation of trust value for Ontology for Genetic Interval took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ogi took 2.5886893272399902s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 8.797645568847656e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.29147958755493164s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00030040740966796875s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ogmd took 2.6493682861328125s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.410743713378906e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.2698221206665039s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.0204012393951416s
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.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006659030914306641s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ogms took 2.5650086402893066s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.482269287109375e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2775001525878906s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.001150369644165039s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omim took 2.7315833568573s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.2687060832977295s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003654956817626953s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omit took 2.6368370056152344s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.26315855979919434s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02056407928466797s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006110668182373047s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-omrse took 2.306549310684204s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.410743713378906e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2446916103363037s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007719993591308594s
Believability | Calculation of trust value for Ontology of Data Mining took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ontodm took 2.49373722076416s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.25982022285461426s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00023603439331054688s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ontodt took 2.570173501968384s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.506111145019531e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.25669074058532715s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006074905395507812s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.498551607131958s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.8160552978515625e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2673516273498535s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009174346923828125s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-opl took 2.5753965377807617s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.38690185546875e-05s
Availability | VoID file availability check for Phenotypic quality took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2461566925048828s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020895719528198242s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008676052093505859s
Believability | Calculation of trust value for Phenotypic quality took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pato took 2.5678651332855225s
Availability | SPARQL endpoint availability check for Physician Data Query took 5.0067901611328125e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.25241947174072266s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008111000061035156s
Believability | Calculation of trust value for Physician Data Query took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pdq took 2.5620734691619873s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.410743713378906e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.25576281547546387s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007905960083007812s
Believability | Calculation of trust value for Pediatric Terminology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-pedterm took 2.550259590148926s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 5.316734313964844e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.29059767723083496s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020375728607177734s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019741058349609375s
Believability | Calculation of trust value for Parasite Experiment Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-peo took 2.61265230178833s
Availability | SPARQL endpoint availability check for PHARE took 4.3392181396484375e-05s
Availability | VoID file availability check for PHARE took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for PHARE took 0.2675752639770508s
Reputation | Calculation of the PageRank for PHARE took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for PHARE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006208419799804688s
Believability | Calculation of trust value for PHARE took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-phare took 2.6404881477355957s
Availability | SPARQL endpoint availability check for PKO_Re took 5.054473876953125e-05s
Availability | VoID file availability check for PKO_Re took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.25307130813598633s
Reputation | Calculation of the PageRank for PKO_Re took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00016736984252929688s
Believability | Calculation of trust value for PKO_Re took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pko took 2.6214699745178223s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.38690185546875e-05s
Availability | VoID file availability check for PMA 2010 took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2799947261810303s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009009838104248047s
Believability | Calculation of trust value for PMA 2010 took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pma took 2.6382248401641846s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 6.318092346191406e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2602355480194092s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020847797393798828s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00016927719116210938s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-pmr took 2.5977954864501953s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.27901411056518555s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00039505958557128906s
Believability | Calculation of trust value for Plant Anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-po took 2.5412437915802s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.935264587402344e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2653064727783203s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020817279815673828s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.818771362304688e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.5751805305480957s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.2592167854309082s
Reputation | Calculation of the PageRank for Plant Ontology took 0.021107912063598633s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004508495330810547s
Believability | Calculation of trust value for Plant Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.602590322494507s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 5.125999450683594e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2538940906524658s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006814002990722656s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pr took 2.5497281551361084s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.267692565917969e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.26418113708496094s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020346641540527344s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00025391578674316406s
Believability | Calculation of trust value for Proteomics data and process provenance took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-propreo took 2.5040268898010254s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.887580871582031e-05s
Availability | VoID file availability check for Pathway ontology took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.2634615898132324s
Reputation | Calculation of the PageRank for Pathway ontology took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00011968612670898438s
Believability | Calculation of trust value for Pathway ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pw took 2.557572364807129s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.2809023857116699s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 2.9087066650390625e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-qibo took 2.5939626693725586s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.506111145019531e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3267381191253662s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017547607421875s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rcd took 2.981921672821045s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2502624988555908s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012445449829101562s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rctontology took 2.5290064811706543s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 6.866455078125e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2477097511291504s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.00011205673217773438s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-repo took 2.558349847793579s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.267692565917969e-05s
Availability | VoID file availability check for Physico-chemical process took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.27714991569519043s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019097328186035156s
Believability | Calculation of trust value for Physico-chemical process took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rex took 2.5841002464294434s
Availability | SPARQL endpoint availability check for RadLex took 4.291534423828125e-05s
Availability | VoID file availability check for RadLex took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for RadLex took 0.26171183586120605s
Reputation | Calculation of the PageRank for RadLex took 0.02093338966369629s
Interlinking | Calculation of Degree of Connection for RadLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015017986297607422s
Believability | Calculation of trust value for RadLex took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rid took 2.559206485748291s
Availability | SPARQL endpoint availability check for RNA ontology took 5.698204040527344e-05s
Availability | VoID file availability check for RNA ontology took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.25435733795166016s
Reputation | Calculation of the PageRank for RNA ontology took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005507469177246094s
Believability | Calculation of trust value for RNA ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-rnao took 2.5956852436065674s
Availability | SPARQL endpoint availability check for Role Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Role Ontology took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2664504051208496s
Reputation | Calculation of the PageRank for Role Ontology took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00020599365234375s
Believability | Calculation of trust value for Role Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-roleo took 2.6244266033172607s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.279590368270874s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020318269729614258s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00017642974853515625s
Believability | Calculation of trust value for Rat Strain Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rs took 2.624267101287842s
Availability | SPARQL endpoint availability check for RxNORM took 4.458427429199219e-05s
Availability | VoID file availability check for RxNORM took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for RxNORM took 0.24594759941101074s
Reputation | Calculation of the PageRank for RxNORM took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006098747253417969s
Believability | Calculation of trust value for RxNORM took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.946871280670166s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.553794860839844e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.27486252784729004s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0009558200836181641s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0011844635009765625s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-sao took 2.5845043659210205s
Availability | SPARQL endpoint availability check for Systems Biology took 7.033348083496094e-05s
Availability | VoID file availability check for Systems Biology took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.2476818561553955s
Reputation | Calculation of the PageRank for Systems Biology took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.000993967056274414s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0005474090576171875s
Believability | Calculation of trust value for Systems Biology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sbo took 2.5533745288848877s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.25130772590637207s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0009467601776123047s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00013136863708496094s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sbro took 2.5805771350860596s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.26584815979003906s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.021343231201171875s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013492107391357422s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sdo took 2.562776565551758s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.410743713378906e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.25096821784973145s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00033211708068847656s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sep took 2.579829454421997s
Availability | SPARQL endpoint availability check for Student Health Record took 4.3392181396484375e-05s
Availability | VoID file availability check for Student Health Record took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.27048230171203613s
Reputation | Calculation of the PageRank for Student Health Record took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004603862762451172s
Believability | Calculation of trust value for Student Health Record took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-shr took 2.6084914207458496s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0009119510650634766s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.25202202796936035s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012009143829345703s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sio took 3.636154890060425s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.482269287109375e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.27791905403137207s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00019741058349609375s
Believability | Calculation of trust value for Situation-Based Access Control took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sitbac took 2.7526838779449463s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 7.414817810058594e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.30065131187438965s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020813941955566406s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0009832382202148438s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.00209808349609375s
Believability | Calculation of trust value for SNOMED Clinical Terms took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-snomedct took 3.0327696800231934s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.26651859283447266s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0007107257843017578s
Believability | Calculation of trust value for SNP-Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-snpo took 2.607423782348633s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.3392181396484375e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2828853130340576s
Reputation | Calculation of the PageRank for Sequence types and features took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005881786346435547s
Believability | Calculation of trust value for Sequence types and features took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.6492013931274414s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.506111145019531e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.30028629302978516s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0017955303192138672s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sopharm took 3.041189670562744s
Availability | SPARQL endpoint availability check for SoyOntology took 4.410743713378906e-05s
Availability | VoID file availability check for SoyOntology took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.25530362129211426s
Reputation | Calculation of the PageRank for SoyOntology took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012493133544921875s
Believability | Calculation of trust value for SoyOntology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-soy took 2.5356056690216064s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.2541069984436035s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.00083160400390625s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00035262107849121094s
Believability | Calculation of trust value for Spider Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-spd took 2.5672736167907715s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2562718391418457s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020821094512939453s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00029850006103515625s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-spto took 2.591885805130005s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.26142311096191406s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00044798851013183594s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sso took 2.6944196224212646s
Availability | SPARQL endpoint availability check for Software Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Software Ontology took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.267486572265625s
Reputation | Calculation of the PageRank for Software Ontology took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004494190216064453s
Believability | Calculation of trust value for Software Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-swo took 2.5818979740142822s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.24345803260803223s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002353191375732422s
Believability | Calculation of trust value for Tick gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-tads took 2.5601179599761963s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 7.033348083496094e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2539405822753906s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02026844024658203s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008795261383056641s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tao took 2.5717830657958984s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.315376281738281e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2609586715698242s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.940696716308594e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-taxrank took 2.5260722637176514s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 6.747245788574219e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.2679119110107422s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.581710815429688e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-teddy took 2.531872272491455s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.26792311668395996s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020177364349365234s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008406639099121094s
Believability | Calculation of trust value for Time Event Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-teo took 2.7531516551971436s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.601478576660156e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.237898588180542s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.0205078125s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003845691680908203s
Believability | Calculation of trust value for Mosquito gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tgma took 2.541032075881958s
Availability | SPARQL endpoint availability check for thesaurus took 4.38690185546875e-05s
Availability | VoID file availability check for thesaurus took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for thesaurus took 0.2551991939544678s
Reputation | Calculation of the PageRank for thesaurus took 0.020734548568725586s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.033348083496094e-05s
Believability | Calculation of trust value for thesaurus took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.582925319671631s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.57763671875e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.257091760635376s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00034356117248535156s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.580650806427002s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 5.6743621826171875e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.27861475944519043s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008428096771240234s
Believability | Calculation of trust value for Translational Medicine Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tmo took 2.679234743118286s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.26309823989868164s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.0208587646484375s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00017952919006347656s
Believability | Calculation of trust value for Plant Trait Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-to took 2.6581618785858154s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2696349620819092s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02076435089111328s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001857280731201172s
Believability | Calculation of trust value for TOK_Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-tok took 2.559579372406006s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.24082374572753906s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020728111267089844s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019812583923339844s
Believability | Calculation of trust value for Teleost taxonomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tto took 2.6304054260253906s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.24509429931640625s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010306835174560547s
Believability | Calculation of trust value for Uber anatomy ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-uberon took 2.56992244720459s
Availability | SPARQL endpoint availability check for Units Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Units Ontology took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.24980711936950684s
Reputation | Calculation of the PageRank for Units Ontology took 0.020696640014648438s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00024890899658203125s
Believability | Calculation of trust value for Units Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.6634626388549805s
Availability | SPARQL endpoint availability check for Units of measurement took 4.3392181396484375e-05s
Availability | VoID file availability check for Units of measurement took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.23933887481689453s
Reputation | Calculation of the PageRank for Units of measurement took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002968311309814453s
Believability | Calculation of trust value for Units of measurement took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-uo took 2.5594828128814697s
Availability | SPARQL endpoint availability check for VANDF took 4.315376281738281e-05s
Availability | VoID file availability check for VANDF took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for VANDF took 0.265519380569458s
Reputation | Calculation of the PageRank for VANDF took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for VANDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006875991821289062s
Believability | Calculation of trust value for VANDF took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vandf took 2.6305339336395264s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.27260875701904297s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004374980926513672s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vao took 2.6201047897338867s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.649162292480469e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.24422454833984375s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020644187927246094s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006186962127685547s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-vhog took 2.6372292041778564s
Availability | SPARQL endpoint availability check for VIVO took 5.5789947509765625e-05s
Availability | VoID file availability check for VIVO took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for VIVO took 0.2563495635986328s
Reputation | Calculation of the PageRank for VIVO took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003535747528076172s
Believability | Calculation of trust value for VIVO took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-vivo took 2.5439603328704834s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.266460657119751s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.021475791931152344s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0010747909545898438s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0013952255249023438s
Believability | Calculation of trust value for Vaccine Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-vo took 2.595957040786743s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.25664258003234863s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020303964614868164s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00021886825561523438s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vt took 2.6250991821289062s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.7206878662109375e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.25221729278564453s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005328655242919922s
Believability | Calculation of trust value for C. elegans gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-wbbt took 2.588620901107788s
Availability | SPARQL endpoint availability check for C. elegans development took 4.482269287109375e-05s
Availability | VoID file availability check for C. elegans development took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2814939022064209s
Reputation | Calculation of the PageRank for C. elegans development took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.2438507080078125e-05s
Believability | Calculation of trust value for C. elegans development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-wbls took 2.635951042175293s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.4345855712890625e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.29219865798950195s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.298324584960938e-05s
Believability | Calculation of trust value for C. elegans phenotype took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.6175458431243896s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.315376281738281e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2743494510650635s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020885229110717773s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006654262542724609s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-who took 2.5327491760253906s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.363059997558594e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2703206539154053s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006692409515380859s
Believability | Calculation of trust value for Xenopus anatomy and development took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-xao took 2.6637258529663086s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.2623746395111084s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00024819374084472656s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-xco took 2.6235592365264893s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.506111145019531e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.28579258918762207s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002701282501220703s
Believability | Calculation of trust value for Yeast phenotypes took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ypo took 2.6497323513031006s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.410743713378906e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.25263547897338867s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02041792869567871s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007457733154296875s
Believability | Calculation of trust value for Zebrafish anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-zfa took 2.560731887817383s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 0.00013446807861328125s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.26950907707214355s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 3.0279159545898438e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.956390380859375e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 7.62939453125e-06s
INFO | --- Analysis for Bioportal_link took 3.8037943840026855s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4364476203918457s
Availability | VoID file availability check for BioSamples RDF took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.26793766021728516s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020290613174438477s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.218650817871094e-05s
Believability | Calculation of trust value for BioSamples RDF took 7.152557373046875e-06s
INFO | --- Analysis for biosamples-rdf took 3.5030312538146973s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.8541474342346191s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.27681541442871094s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.021131515502929688s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0008730888366699219s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.000125885009765625s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for bis-linked-data took 3.2268476486206055s
Availability | SPARQL endpoint availability check for Bitzi took 4.1961669921875e-05s
Availability | VoID file availability check for Bitzi took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Bitzi took 0.28890442848205566s
Reputation | Calculation of the PageRank for Bitzi took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for Bitzi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Bitzi took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bitzi took 7.867813110351562e-06s
INFO | --- Analysis for bitzi took 2.8352603912353516s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.649162292480469e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.28241395950317383s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for BizkaiSense took 0.000820159912109375s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.743171691894531e-05s
Believability | Calculation of trust value for BizkaiSense took 7.867813110351562e-06s
INFO | --- Analysis for bizkaisense took 2.8561301231384277s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.458427429199219e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.26326489448547363s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.9087066650390625e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.62939453125e-06s
INFO | --- Analysis for blabla-itemlist took 2.871443271636963s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.2438507080078125e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.24994969367980957s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0010304450988769531s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.790855407714844e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.3909759521484375e-06s
INFO | --- Analysis for blabla_itemlist took 2.9266750812530518s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2573237419128418s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.790855407714844e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for bll-thesaurus took 3.5799782276153564s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 0.5110635757446289s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.28159046173095703s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020506620407104492s
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.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.651878356933594e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for bluk-bnb took 10.736507892608643s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.32057690620422363s
Availability | VoID file availability check for Thesaurus BNCF took 0.0007317066192626953s
Extra | Recovery of all triples for Thesaurus BNCF took 48.14983248710632s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6162467002868652s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6493303775787354s
Interoperability | New terms check for Thesaurus BNCF took 1.558401346206665s
Versatility | Languages check for Thesaurus BNCF took 6.808495998382568s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8771584033966064s
Security | Check HTTPS for Thesaurus BNCF took 0.08393263816833496s
Interpretability | RDF structures check for Thesaurus BNCF took 0.12178707122802734s
Versatility | Serialization formats check for Thesaurus BNCF took 0.12918305397033691s
Availability | RDF dump link check for Thesaurus BNCF took 0.12245678901672363s
License | MR license check for Thesaurus BNCF took 0.13003325462341309s
License | HR license check for Thesaurus BNCF took 0.2276930809020996s
Amount of data | Number of property check for Thesaurus BNCF took 0.13024115562438965s
Understandability | Number of label check for Thesaurus BNCF took 0.25786447525024414s
Understandability | URI regex check for Thesaurus BNCF took 0.2656087875366211s
Understandability | Vocabs check for Thesaurus BNCF took 0.12137436866760254s
Verifiability | Authors check for Thesaurus BNCF took 0.13133835792541504s
Verifiability | Publishers check for Thesaurus BNCF took 0.1318037509918213s
Performance | Throughput check for Thesaurus BNCF took 10.863480806350708s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.128715515136719e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.13512063026428223s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.1295185089111328s
Interlinking | skos check for Thesaurus BNCF took 0.18962693214416504s
Interlinking | skos check for Thesaurus BNCF took 0.17553424835205078s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.1255054473876953s
Currency | Creation date check for Thesaurus BNCF took 0.2643263339996338s
Currency | Modification date check for Thesaurus BNCF took 0.26975321769714355s
Rep.Conc. | URIs length for Thesaurus BNCF took 25.37457275390625s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.12109065055847168s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.12526369094848633s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.1293163299560547s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.317091226577759s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5151181221008301s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.060252666473389s
Consistency | Disjoint class check for Thesaurus BNCF took 0.13035321235656738s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8693790435791016s
Consistency | Misplaced classes for Thesaurus BNCF took 7.127353668212891s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.912605285644531s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.5705370903015137s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.3374500274658203s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.467931032180786s
Security | Sign check for Thesaurus BNCF took 0.11772370338439941s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 22.45041799545288s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3548550605773926s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.033348083496094e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.9073486328125e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 7.3909759521484375e-06s
INFO | --- Analysis for bncf-ns took 193.90845847129822s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 27.62015986442566s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0008263587951660156s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 46.26509165763855s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 107.95530843734741s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.41591215133667s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 21.863768100738525s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 85.47717046737671s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 25.603936195373535s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.11755681037903s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.52204656600952s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 20.120911359786987s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 23.875178337097168s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.327884435653687s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 85.02184081077576s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 22.460294246673584s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 22.405611038208008s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 51.72071814537048s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 18.436378240585327s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.817448616027832s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 28.109464168548584s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 254.73062705993652s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.440017700195312e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.06412100791931s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 28.8278706073761s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.495314121246338s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 27.614660501480103s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.044796466827393s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 57.71430993080139s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 23.739046335220337s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 65.83896040916443s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 25.301376581192017s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 21.80918836593628s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 28.77135705947876s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 23.341495037078857s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02416849136352539s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030025482177734375s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 28.71387028694153s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.22288227081299s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 29.579018115997314s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8899314403533936s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 28.17561411857605s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.029276132583618164s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 23.515419960021973s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 29.759581327438354s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.012622356414795s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1860222816467285s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1444091796875e-05s
INFO | --- Analysis for bpr took 6561.8930768966675s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.9591064453125e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.2742898464202881s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020765304565429688s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0009210109710693359s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 8.177757263183594e-05s
Believability | Calculation of trust value for Brazilian Politicians took 5.245208740234375e-06s
INFO | --- Analysis for brazilian-politicians took 4.507069110870361s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.315376281738281e-05s
Availability | VoID file availability check for BrazilianCities took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.2590775489807129s
Reputation | Calculation of the PageRank for BrazilianCities took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 2.9325485229492188e-05s
Believability | Calculation of trust value for BrazilianCities took 7.62939453125e-06s
INFO | --- Analysis for braziliancities took 3.371185779571533s
Availability | SPARQL endpoint availability check for Bricklink took 1.7963972091674805s
Availability | VoID file availability check for Bricklink took 0.0003807544708251953s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2827117443084717s
Reputation | Calculation of the PageRank for Bricklink took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.224082946777344e-05s
Believability | Calculation of trust value for Bricklink took 7.3909759521484375e-06s
INFO | --- Analysis for bricklink took 10.97971773147583s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.111924648284912s
Availability | VoID file availability check for British Museum Collection took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.27079176902770996s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.170967102050781e-05s
Believability | Calculation of trust value for British Museum Collection took 6.67572021484375e-06s
INFO | --- Analysis for british-museum-collection took 73.14090204238892s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.482269287109375e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.25168585777282715s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.023340225219726562s
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.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.933906555175781e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 7.867813110351562e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.8310418128967285s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.267692565917969e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.2766580581665039s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02073383331298828s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0009181499481201172s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 3.504753112792969e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 7.3909759521484375e-06s
INFO | --- Analysis for bsv took 3.7766597270965576s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.4738237857818604s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2926769256591797s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.020750761032104492s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3828277587890625e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.9141387939453125e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 5.926380157470703s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.1961669921875e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.27416253089904785s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.8623809814453125e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 7.867813110351562e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.962416648864746s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.76837158203125e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.2677192687988281s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020869731903076172s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 2.9325485229492188e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 6.9141387939453125e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.8443260192871094s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.5977435111999512s
Availability | VoID file availability check for business.data.gov.uk took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.27025580406188965s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.030632019042969e-05s
Believability | Calculation of trust value for business.data.gov.uk took 6.198883056640625e-06s
INFO | --- Analysis for business-data-gov-uk took 3.116394281387329s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5593338012695312s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0006420612335205078s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.512589454650879s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.6508638858795166s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.4393339157104492s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7942111492156982s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 43.93644046783447s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.3549997806549072s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.18319010734558105s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5835142135620117s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3724343776702881s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.3578779697418213s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.43870997428894043s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.757795810699463s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3454303741455078s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.8448314666748047s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.7310938835144043s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.33377861976623535s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 1.020885705947876s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3972928524017334s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.697648525238037s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.724761962890625e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.33922743797302246s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3564789295196533s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.4398927688598633s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3167581558227539s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.36022162437438965s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.6735389232635498s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.71590256690979s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.3290786743164062s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.3341672420501709s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4931972026824951s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5136549472808838s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.2331748008728027s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.034044742584228516s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.028614044189453125s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.41974520683288574s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.5553269386291504s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.4020216464996338s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.245969533920288s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.309809684753418s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.51883864402771s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03252840042114258s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.34271740913391113s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.3812284469604492s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 10106.423707485199s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 2.2097280025482178s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.9634630680084229s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 0.006786346435546875s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.004285097122192383s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 0.037400007247924805s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 5.245208740234375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 0.0003082752227783203s
INFO | --- Analysis for BVMC took 10345.126813173294s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 0.00025010108947753906s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.7205302715301514s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.02066946029663086s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.266334533691406e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 9.059906005859375e-06s
INFO | --- Analysis for cabbage took 4.974123001098633s
Availability | SPARQL endpoint availability check for cablegate took 1.771049976348877s
Availability | VoID file availability check for cablegate took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for cablegate took 0.2527501583099365s
Reputation | Calculation of the PageRank for cablegate took 0.02869248390197754s
Interlinking | Calculation of Degree of Connection for cablegate took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.890296936035156e-05s
Believability | Calculation of trust value for cablegate took 8.344650268554688e-06s
INFO | --- Analysis for cablegate took 17.86242175102234s
Availability | SPARQL endpoint availability check for Calames took 4.363059997558594e-05s
Availability | VoID file availability check for Calames took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Calames took 0.2650027275085449s
Reputation | Calculation of the PageRank for Calames took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for Calames took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Calames took 3.8623809814453125e-05s
Believability | Calculation of trust value for Calames took 7.62939453125e-06s
INFO | --- Analysis for calames took 4.563607931137085s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.4664442539215088s
Availability | VoID file availability check for CaLiGraph took 0.00026488304138183594s
Extra | Recovery of all triples for CaLiGraph took 2.2113423347473145s
Performance | Total latancy measurement for CaLiGraph took 1.277660608291626s
Amount of data | Number of triples check for CaLiGraph took 11.795206546783447s
Interoperability | New terms check for CaLiGraph took 14.391918420791626s
Versatility | Languages check for CaLiGraph took 60.31623911857605s
Interpretability | Number of blank nodes check for CaLiGraph took 0.26274824142456055s
Security | Check HTTPS for CaLiGraph took 0.12908649444580078s
Interpretability | RDF structures check for CaLiGraph took 0.46422433853149414s
Versatility | Serialization formats check for CaLiGraph took 0.3471856117248535s
Availability | RDF dump link check for CaLiGraph took 0.2693064212799072s
License | MR license check for CaLiGraph took 0.44640636444091797s
License | HR license check for CaLiGraph took 60.30566143989563s
Amount of data | Number of property check for CaLiGraph took 0.2554492950439453s
Understandability | Number of label check for CaLiGraph took 4.595620393753052s
Understandability | URI regex check for CaLiGraph took 0.5633115768432617s
Understandability | Vocabs check for CaLiGraph took 0.27314305305480957s
Verifiability | Authors check for CaLiGraph took 0.2857484817504883s
Verifiability | Publishers check for CaLiGraph took 0.2603151798248291s
Performance | Throughput check for CaLiGraph took 11.641435623168945s
Amount of data | Check the number of entities for CaLiGraph took 0.0270693302154541s
Verifiability | Contribs. check for CaLiGraph took 0.26001930236816406s
Interlinking | sameAs chians check for CaLiGraph took 0.6972160339355469s
Interlinking | skos check for CaLiGraph took 0.40424489974975586s
Interlinking | skos check for CaLiGraph took 0.2203528881072998s
Timeliness | dataset update frequency check for CaLiGraph took 0.3294038772583008s
Currency | Creation date check for CaLiGraph took 0.6072771549224854s
Currency | Modification date check for CaLiGraph took 0.5679905414581299s
Rep.Conc. | URIs length for CaLiGraph took 61.10899305343628s
Interoperability | New vocabularies check for CaLiGraph took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.260265588760376s
Accuracy | Check Functional Property for CaLiGraph took 0.2883327007293701s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.31485819816589355s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.630192756652832s
Accuracy | Check White space in annotation for CaLiGraph took 0.026537418365478516s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05006551742553711s
Consistency | Disjoint class check for CaLiGraph took 0.25209712982177734s
Consistency | Check Misplaced properties for CaLiGraph took 61.20514893531799s
Consistency | Misplaced classes for CaLiGraph took 0.4963366985321045s
Consistency | Check Ontology hijacking for CaLiGraph took 2.097397565841675s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2916076183319092s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.58329629898071s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03296947479248047s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.45479655265808105s
Security | Sign check for CaLiGraph took 0.4027421474456787s
Availability | Check URIs Dereferenciability for CaLiGraph took 11.753539562225342s
Completeness | Calculation of interlinking completeness for CaLiGraph took 1.208728551864624s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.552436828613281e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 9.5367431640625e-06s
INFO | --- Analysis for CaLiGraph took 1482.569832086563s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.23551464080810547s
Availability | VoID file availability check for CaLiGraph took 0.0006651878356933594s
Extra | Recovery of all triples for CaLiGraph took 1.794985055923462s
Performance | Total latancy measurement for CaLiGraph took 1.185603141784668s
Amount of data | Number of triples check for CaLiGraph took 11.753926992416382s
Interoperability | New terms check for CaLiGraph took 2.2714881896972656s
Versatility | Languages check for CaLiGraph took 60.28889441490173s
Interpretability | Number of blank nodes check for CaLiGraph took 0.258617639541626s
Security | Check HTTPS for CaLiGraph took 0.1403517723083496s
Interpretability | RDF structures check for CaLiGraph took 0.26258015632629395s
Versatility | Serialization formats check for CaLiGraph took 0.26819849014282227s
Availability | RDF dump link check for CaLiGraph took 0.2523829936981201s
License | MR license check for CaLiGraph took 0.2882983684539795s
License | HR license check for CaLiGraph took 60.30629372596741s
Amount of data | Number of property check for CaLiGraph took 0.2458178997039795s
Understandability | Number of label check for CaLiGraph took 3.0831334590911865s
Understandability | URI regex check for CaLiGraph took 0.5109274387359619s
Understandability | Vocabs check for CaLiGraph took 0.23628687858581543s
Verifiability | Authors check for CaLiGraph took 0.2600395679473877s
Verifiability | Publishers check for CaLiGraph took 0.2613043785095215s
Performance | Throughput check for CaLiGraph took 11.550705432891846s
Amount of data | Check the number of entities for CaLiGraph took 0.011574745178222656s
Verifiability | Contribs. check for CaLiGraph took 0.2617359161376953s
Interlinking | sameAs chians check for CaLiGraph took 0.6637847423553467s
Interlinking | skos check for CaLiGraph took 0.2373805046081543s
Interlinking | skos check for CaLiGraph took 0.22197413444519043s
Timeliness | dataset update frequency check for CaLiGraph took 0.24512410163879395s
Currency | Creation date check for CaLiGraph took 0.532243013381958s
Currency | Modification date check for CaLiGraph took 0.5262932777404785s
Rep.Conc. | URIs length for CaLiGraph took 61.19349527359009s
Interoperability | New vocabularies check for CaLiGraph took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2670450210571289s
Accuracy | Check Functional Property for CaLiGraph took 0.25295448303222656s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.26476216316223145s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6582546234130859s
Accuracy | Check White space in annotation for CaLiGraph took 0.02656388282775879s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05071616172790527s
Consistency | Disjoint class check for CaLiGraph took 0.25612401962280273s
Consistency | Check Misplaced properties for CaLiGraph took 61.05418825149536s
Consistency | Misplaced classes for CaLiGraph took 0.6257500648498535s
Consistency | Check Ontology hijacking for CaLiGraph took 2.0702333450317383s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2839813232421875s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.63546872138977s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.02967381477355957s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.5038323402404785s
Security | Sign check for CaLiGraph took 0.27067136764526367s
Availability | Check URIs Dereferenciability for CaLiGraph took 11.778202056884766s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.896134614944458s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.295608520507812e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 9.775161743164062e-06s
INFO | --- Analysis for caligraph took 1466.7839035987854s
Availability | SPARQL endpoint availability check for can-link took 4.506111145019531e-05s
Availability | VoID file availability check for can-link took 0.0003349781036376953s
Completeness | Calculation of interlinking completeness for can-link took 0.717071533203125s
Reputation | Calculation of the PageRank for can-link took 0.021106243133544922s
Interlinking | Calculation of Degree of Connection for can-link took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for can-link took 0.0009298324584960938s
Interlinking | Calculation of Clustering coefficient for can-link took 3.4809112548828125e-05s
Believability | Calculation of trust value for can-link took 7.62939453125e-06s
INFO | --- Analysis for can-link took 5.1902992725372314s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.06705832481384277s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.6989810466766357s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 7.867813110351562e-06s
INFO | --- Analysis for cap-italy-rdf took 2.977407455444336s
Availability | SPARQL endpoint availability check for person took 4.315376281738281e-05s
Availability | VoID file availability check for person took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for person took 0.7025027275085449s
Reputation | Calculation of the PageRank for person took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for person took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for person took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for person took 2.8848648071289062e-05s
Believability | Calculation of trust value for person took 7.3909759521484375e-06s
INFO | --- Analysis for card took 3.2026095390319824s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 5.53131103515625e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007460117340087891s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.26336669921875s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0009267330169677734s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.458427429199219e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 9.298324584960938e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.4313347339630127s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.1961669921875e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.2551851272583008s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 2.8371810913085938e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 7.867813110351562e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.8955252170562744s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.5929205417633057s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.000255584716796875s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 135.98002576828003s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 1.0889418125152588s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 10.99997067451477s
Interoperability | New terms check for Norway catch records dataset @PSNC took 16.067243337631226s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.2058346271515s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 3.3343045711517334s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.30562663078308105s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 10.59157657623291s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.32250404357910156s
License | MR license check for Norway catch records dataset @PSNC took 0.3390183448791504s
License | HR license check for Norway catch records dataset @PSNC took 300.2484726905823s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.30526065826416016s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.341442346572876s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.5951719284057617s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.490398645401001s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.20465755462646484s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.2682466506958008s
Performance | Throughput check for Norway catch records dataset @PSNC took 10.972707033157349s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.319450378417969e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.20102381706237793s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.19291186332702637s
Interlinking | skos check for Norway catch records dataset @PSNC took 1.3489677906036377s
Interlinking | skos check for Norway catch records dataset @PSNC took 1.3006072044372559s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 6.861560344696045s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.463625431060791s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.24588942527770996s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 149.7787790298462s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.21193456649780273s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.37183594703674316s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.32777857780456543s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 48.33617544174194s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.698767900466919s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.6357967853546143s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.19798016548156738s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 84.75904583930969s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.555938959121704s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 43.23403811454773s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.5088610649108887s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 86.15156745910645s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.776984214782715s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.68808913230896s
Security | Sign check for Norway catch records dataset @PSNC took 0.4359443187713623s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 9.284364938735962s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 1.6519103050231934s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.020815372467041016s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2308.231783390045s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.458427429199219e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0009760856628417969s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.2911696434020996s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020861148834228516s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010013580322265625s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 7.3909759521484375e-06s
INFO | --- Analysis for ce4r took 195.04156827926636s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.47481226921081543s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002624988555908203s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.5667510032653809s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.853825569152832s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2869596481323242s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.7132489681243896s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.15604090690613s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16767287254333496s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3859708309173584s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16672563552856445s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14470171928405762s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21907401084899902s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.32236409187316895s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16380071640014648s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2650728225708008s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3245565891265869s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1797349452972412s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.25319576263427734s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18919754028320312s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.852830410003662s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.224082946777344e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17202520370483398s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1390399932861328s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.30788445472717285s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1406688690185547s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15900421142578125s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.36135387420654297s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3596153259277344s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.2084927558898926s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16897130012512207s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.18813776969909668s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.16669774055480957s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.8655693531036377s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.029210567474365234s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.028639554977416992s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19306206703186035s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2011706829071045s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.049179792404175s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.3164348602294922s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4892945289611816s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.031197071075439453s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.2009572982788086s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1428065299987793s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2954.5832285881042s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.5407848358154297s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.315376281738281e-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 8.344650268554688e-06s
INFO | --- Analysis for ceo took 3080.611834049225s
Availability | SPARQL endpoint availability check for Charging Stations took 5.745887756347656e-05s
Availability | VoID file availability check for Charging Stations took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.26456713676452637s
Reputation | Calculation of the PageRank for Charging Stations took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for Charging Stations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 2.9325485229492188e-05s
Believability | Calculation of trust value for Charging Stations took 1.1920928955078125e-05s
INFO | --- Analysis for charging-stations took 3.3850419521331787s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.506111145019531e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.27573370933532715s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.337860107421875e-05s
Believability | Calculation of trust value for Chat Game corpus took 8.821487426757812e-06s
INFO | --- Analysis for chat-game-corpus took 12.938811540603638s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.3392181396484375e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.28952813148498535s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 7.3909759521484375e-06s
INFO | --- Analysis for chebi took 3.7990987300872803s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.38690185546875e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.6883764266967773s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020700931549072266s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.817413330078125e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.621246337890625e-05s
INFO | --- Analysis for chem2bio2rdf took 137.63610863685608s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.6547434329986572s
Availability | VoID file availability check for ChEMBL RDF took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.25612711906433105s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.9114227294921875e-05s
Believability | Calculation of trust value for ChEMBL RDF took 7.3909759521484375e-06s
INFO | --- Analysis for chembl-rdf took 4.566997766494751s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.0301909446716309s
Availability | VoID file availability check for chemdb  dataset took 0.00029659271240234375s
Extra | Recovery of all triples for chemdb  dataset took 10.917374849319458s
Performance | Total latancy measurement for chemdb  dataset took 2.5841164588928223s
Amount of data | Number of triples check for chemdb  dataset took 0.5627248287200928s
Interoperability | New terms check for chemdb  dataset took 3.989689350128174s
Versatility | Languages check for chemdb  dataset took 28.961364030838013s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5464167594909668s
Interpretability | RDF structures check for chemdb  dataset took 0.5599884986877441s
Versatility | Serialization formats check for chemdb  dataset took 1.5882701873779297s
Availability | RDF dump link check for chemdb  dataset took 0.9386837482452393s
License | MR license check for chemdb  dataset took 3.2906558513641357s
License | HR license check for chemdb  dataset took 4.201804876327515s
Amount of data | Number of property check for chemdb  dataset took 0.5453097820281982s
Understandability | Number of label check for chemdb  dataset took 5.413170576095581s
Understandability | URI regex check for chemdb  dataset took 2.2657480239868164s
Understandability | Vocabs check for chemdb  dataset took 0.872169017791748s
Verifiability | Authors check for chemdb  dataset took 1.2212624549865723s
Verifiability | Publishers check for chemdb  dataset took 0.8838808536529541s
Performance | Throughput check for chemdb  dataset took 10.7141752243042s
Amount of data | Check the number of entities for chemdb  dataset took 6.175041198730469e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.8908207416534424s
Interlinking | sameAs chians check for chemdb  dataset took 1.1360993385314941s
Interlinking | skos check for chemdb  dataset took 2.329911470413208s
Interlinking | skos check for chemdb  dataset took 0.5328350067138672s
Timeliness | dataset update frequency check for chemdb  dataset took 1.2227087020874023s
Currency | Creation date check for chemdb  dataset took 1.3989357948303223s
Currency | Modification date check for chemdb  dataset took 1.0301990509033203s
Rep.Conc. | URIs length for chemdb  dataset took 3.4560458660125732s
Interoperability | New vocabularies check for chemdb  dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5430610179901123s
Accuracy | Check Functional Property for chemdb  dataset took 0.883312463760376s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.8408019542694092s
Accuracy | Check Empty annotation labels for chemdb  dataset took 3.6864280700683594s
Accuracy | Check White space in annotation for chemdb  dataset took 0.031019210815429688s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03286457061767578s
Consistency | Disjoint class check for chemdb  dataset took 0.6930382251739502s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2689905166625977s
Consistency | Misplaced classes for chemdb  dataset took 0.6222062110900879s
Consistency | Check Ontology hijacking for chemdb  dataset took 4.207594633102417s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.2916336059570312s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.0152018070220947s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03201460838317871s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.52382493019104s
Security | Sign check for chemdb  dataset took 1.568549394607544s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2747.5253427028656s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 1.3971850872039795s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.02131032943725586s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 6.818771362304688e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb  dataset took 7.3909759521484375e-06s
INFO | --- Analysis for chemdb-basicInfo took 3857.9642746448517s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5274012088775635s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0004229545593261719s
Extra | Recovery of all triples for chemdb estimated properties dataset took 14.865723609924316s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.5594680309295654s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5733742713928223s
Interoperability | New terms check for chemdb estimated properties dataset took 4.029160976409912s
Versatility | Languages check for chemdb estimated properties dataset took 26.895598888397217s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5303964614868164s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5200934410095215s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.4312293529510498s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.7991588115692139s
License | MR license check for chemdb estimated properties dataset took 2.569767951965332s
License | HR license check for chemdb estimated properties dataset took 4.090445041656494s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5390188694000244s
Understandability | Number of label check for chemdb estimated properties dataset took 4.805444955825806s
Understandability | URI regex check for chemdb estimated properties dataset took 1.918107509613037s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.7917788028717041s
Verifiability | Authors check for chemdb estimated properties dataset took 1.114194393157959s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.7945878505706787s
Performance | Throughput check for chemdb estimated properties dataset took 11.184250116348267s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 8.296966552734375e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.8083186149597168s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.0141074657440186s
Interlinking | skos check for chemdb estimated properties dataset took 1.9151976108551025s
Interlinking | skos check for chemdb estimated properties dataset took 0.4946327209472656s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.0744810104370117s
Currency | Creation date check for chemdb estimated properties dataset took 1.351968765258789s
Currency | Modification date check for chemdb estimated properties dataset took 1.114741563796997s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 3.5570883750915527s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.5175826549530029s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.7992675304412842s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7652301788330078s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 3.1324384212493896s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.030808448791503906s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03414106369018555s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.8525547981262207s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2726538181304932s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6235888004302979s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 4.183526277542114s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.3163270950317383s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 2.0227742195129395s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03249406814575195s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5333671569824219s
Security | Sign check for chemdb estimated properties dataset took 2.0236220359802246s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2731.7963330745697s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 1.436126708984375s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.0213623046875s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 6.604194641113281e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 7.152557373046875e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 3853.040046453476s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5530991554260254s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0002701282501220703s
Extra | Recovery of all triples for chemdb phase transition dataset took 15.835611820220947s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.535090684890747s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5588428974151611s
Interoperability | New terms check for chemdb phase transition dataset took 4.22767448425293s
Versatility | Languages check for chemdb phase transition dataset took 28.677206993103027s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.540733814239502s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5342574119567871s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.6034774780273438s
Availability | RDF dump link check for chemdb phase transition dataset took 0.8702561855316162s
License | MR license check for chemdb phase transition dataset took 3.0942800045013428s
License | HR license check for chemdb phase transition dataset took 4.134676456451416s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5305733680725098s
Understandability | Number of label check for chemdb phase transition dataset took 5.441588878631592s
Understandability | URI regex check for chemdb phase transition dataset took 1.9735090732574463s
Understandability | Vocabs check for chemdb phase transition dataset took 0.8439047336578369s
Verifiability | Authors check for chemdb phase transition dataset took 1.1929352283477783s
Verifiability | Publishers check for chemdb phase transition dataset took 0.8405013084411621s
Performance | Throughput check for chemdb phase transition dataset took 10.379933595657349s
Amount of data | Check the number of entities for chemdb phase transition dataset took 0.00011134147644042969s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.8449230194091797s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.2050259113311768s
Interlinking | skos check for chemdb phase transition dataset took 2.1342780590057373s
Interlinking | skos check for chemdb phase transition dataset took 0.5164237022399902s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.1555359363555908s
Currency | Creation date check for chemdb phase transition dataset took 1.3821687698364258s
Currency | Modification date check for chemdb phase transition dataset took 1.0515167713165283s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.7399582862854004s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.5002768039703369s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.8064754009246826s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.778827428817749s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 3.3579578399658203s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030356407165527344s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03339529037475586s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.6461622714996338s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2891106605529785s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6226646900177002s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 4.29347562789917s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.329533338546753s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.084343671798706s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.0362401008605957s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5298051834106445s
Security | Sign check for chemdb phase transition dataset took 2.159015655517578s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2849.1185278892517s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 1.3981177806854248s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021396875381469727s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.841255187988281e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 8.58306884765625e-06s
INFO | --- Analysis for chemdb-phaseTransition took 3972.7653107643127s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5410809516906738s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.00026035308837890625s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 15.43143606185913s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.598665714263916s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5638494491577148s
Interoperability | New terms check for chemdb thermochemistry dataset took 4.7135467529296875s
Versatility | Languages check for chemdb thermochemistry dataset took 27.823437213897705s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5319340229034424s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.54917311668396s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.500786542892456s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.8632712364196777s
License | MR license check for chemdb thermochemistry dataset took 3.212095022201538s
License | HR license check for chemdb thermochemistry dataset took 4.048296928405762s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5349512100219727s
Understandability | Number of label check for chemdb thermochemistry dataset took 4.918054819107056s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.8231453895568848s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.8522298336029053s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.1960954666137695s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.8674306869506836s
Performance | Throughput check for chemdb thermochemistry dataset took 11.244231700897217s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.390975952148438e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.8513872623443604s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.1758155822753906s
Interlinking | skos check for chemdb thermochemistry dataset took 2.1290030479431152s
Interlinking | skos check for chemdb thermochemistry dataset took 0.51564621925354s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 2.156834840774536s
Currency | Creation date check for chemdb thermochemistry dataset took 1.1532182693481445s
Currency | Modification date check for chemdb thermochemistry dataset took 2.1151585578918457s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.715451717376709s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.4964456558227539s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.5687375068664551s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.8022544384002686s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 3.5604608058929443s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.030301332473754883s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03362154960632324s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.8328759670257568s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.252004861831665s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6245157718658447s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 4.323646783828735s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.3358745574951172s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.056579828262329s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03572988510131836s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5380432605743408s
Security | Sign check for chemdb thermochemistry dataset took 2.129556894302368s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2799.9940643310547s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 1.457672357559204s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.021087169647216797s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.222724914550781e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.1444091796875e-05s
INFO | --- Analysis for chemdb-thermochemistry took 3928.7486107349396s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.267692565917969e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.7089931964874268s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.0040740966796875e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.2874603271484375e-05s
INFO | --- Analysis for chempedia-rdf took 11.41107988357544s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.38690185546875e-05s
Availability | VoID file availability check for Chiman Maru took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.7087092399597168s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 2.956390380859375e-05s
Believability | Calculation of trust value for Chiman Maru took 7.3909759521484375e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 3.14392352104187s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.3491985797882s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.6966831684112549s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.021046876907348633s
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.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.409385681152344e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 799.463636636734s
Availability | SPARQL endpoint availability check for Chronicling America took 4.4345855712890625e-05s
Availability | VoID file availability check for Chronicling America took 0.00040602684020996094s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.7490050792694092s
Reputation | Calculation of the PageRank for Chronicling America took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for Chronicling America took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010824203491210938s
Believability | Calculation of trust value for Chronicling America took 6.9141387939453125e-06s
INFO | --- Analysis for chronicling-america took 12.769315719604492s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.8323979377746582s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0003399848937988281s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 112.40795016288757s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.5205457210540771s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6349344253540039s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.2175240516662598s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.518043041229248s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5721213817596436s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.2957770824432373s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.32410717010498047s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 12.166735410690308s
License | MR license check for Cultural Heritage Thesaurus took 0.3014850616455078s
License | HR license check for Cultural Heritage Thesaurus took 0.41542887687683105s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3485727310180664s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.32408666610717773s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.612114667892456s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.32218360900878906s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.32007551193237305s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.31197571754455566s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.012234449386597s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.367134094238281e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.29431915283203125s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.3313174247741699s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3089182376861572s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.32792043685913086s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.31826019287109375s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6720378398895264s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.7262277603149414s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 14.044351816177368s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.33481574058532715s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.3339059352874756s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.32427406311035156s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 3.390099287033081s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22215843200683594s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3110325336456299s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.0152618885040283s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.30119872093200684s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 7.928271532058716s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.7519869804382324s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00017762184143066406s
Security | Sign check for Cultural Heritage Thesaurus took 0.36160874366760254s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 342.67034125328064s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 1.4965016841888428s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.5490529537200928s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 0.0011341571807861328s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0030355453491210938s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.0170443058013916s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 0.00011086463928222656s
INFO | --- Analysis for cht took 554.543773651123s
Availability | SPARQL endpoint availability check for ciard-ring took 4.76837158203125e-05s
Availability | VoID file availability check for ciard-ring took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.6945722103118896s
Reputation | Calculation of the PageRank for ciard-ring took 0.02080082893371582s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.649162292480469e-05s
Believability | Calculation of trust value for ciard-ring took 1.1444091796875e-05s
INFO | --- Analysis for ciard-ring took 5.377393484115601s
Availability | SPARQL endpoint availability check for Cine Figure took 4.1961669921875e-05s
Availability | VoID file availability check for Cine Figure took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.6868538856506348s
Reputation | Calculation of the PageRank for Cine Figure took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.4345855712890625e-05s
Believability | Calculation of trust value for Cine Figure took 7.3909759521484375e-06s
INFO | --- Analysis for Cine_Figure took 4.182709693908691s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 22.0539972782135s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007994174957275391s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.710843563079834s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020946264266967773s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.14984130859375e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 175.97264051437378s
Availability | SPARQL endpoint availability check for CIPFA took 4.601478576660156e-05s
Availability | VoID file availability check for CIPFA took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for CIPFA took 0.2704453468322754s
Reputation | Calculation of the PageRank for CIPFA took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.647804260253906e-05s
Believability | Calculation of trust value for CIPFA took 5.7220458984375e-06s
INFO | --- Analysis for cipfa took 4.095727920532227s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.04870629310608s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0007870197296142578s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.7369968891143799s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.021114110946655273s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0009772777557373047s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0004596710205078125s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.2874603271484375e-05s
INFO | --- Analysis for ckan took 265.70286297798157s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.48037147521972656s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6971981525421143s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.026293039321899414s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0008668899536132812s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.482269287109375e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 8.58306884765625e-06s
INFO | --- Analysis for CLaSSES took 4.891316652297974s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 9.775161743164062e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2832038402557373s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020913362503051758s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.266334533691406e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.1682510375976562e-05s
INFO | --- Analysis for classical_temples took 4.4779953956604s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 2.048942804336548s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2716844081878662s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.021575450897216797s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.559226989746094e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 9.059906005859375e-06s
INFO | --- Analysis for clean-energy-data-reegle took 9.285132646560669s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.363059997558594e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.27945566177368164s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020638227462768555s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 8.559226989746094e-05s
Believability | Calculation of trust value for CLLD-afbo took 7.867813110351562e-06s
INFO | --- Analysis for clld-afbo took 3.868180990219116s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.553794860839844e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.25797200202941895s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.025127410888671875s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 9.417533874511719e-05s
Believability | Calculation of trust value for CLLD-APICS took 7.152557373046875e-06s
INFO | --- Analysis for clld-apics took 3.5135080814361572s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.24773311614990234s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02046346664428711s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.814697265625e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 7.3909759521484375e-06s
INFO | --- Analysis for clld-ewave took 3.545851945877075s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.363059997558594e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2452249526977539s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.775161743164062e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 7.152557373046875e-06s
INFO | --- Analysis for clld-glottolog took 3.4672582149505615s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.27173519134521484s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020751953125s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0010309219360351562s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 9.489059448242188e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 7.3909759521484375e-06s
INFO | --- Analysis for clld-phoible took 3.452709674835205s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.363059997558594e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.29019832611083984s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.02103734016418457s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.034706115722656e-05s
Believability | Calculation of trust value for CLLD-SAILS took 7.62939453125e-06s
INFO | --- Analysis for clld-sails took 3.657258987426758s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.3392181396484375e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2566194534301758s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 7.796287536621094e-05s
Believability | Calculation of trust value for CLLD-WALS took 7.62939453125e-06s
INFO | --- Analysis for clld-wals took 3.514962911605835s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.482269287109375e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.26361513137817383s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.796287536621094e-05s
Believability | Calculation of trust value for CLLD-WOLD took 8.106231689453125e-06s
INFO | --- Analysis for clld-wold took 3.4026663303375244s
Availability | SPARQL endpoint availability check for COD inventory took 4.267692565917969e-05s
Availability | VoID file availability check for COD inventory took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for COD inventory took 0.25607967376708984s
Reputation | Calculation of the PageRank for COD inventory took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.147125244140625e-05s
Believability | Calculation of trust value for COD inventory took 8.106231689453125e-06s
INFO | --- Analysis for cod-inventory took 2.829354763031006s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.16073942184448242s
Availability | VoID file availability check for Cooperation Databank took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.2392587661743164s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.504753112792969e-05s
Believability | Calculation of trust value for Cooperation Databank took 8.821487426757812e-06s
INFO | --- Analysis for CoDa took 2.6404061317443848s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.2438507080078125e-05s
Availability | VoID file availability check for CODE Endpoint took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.26047658920288086s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.0279159545898438e-05s
Believability | Calculation of trust value for CODE Endpoint took 6.198883056640625e-06s
INFO | --- Analysis for code-endpoint took 2.9474170207977295s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.40201497077941895s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.25794553756713867s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02068305015563965s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.123283386230469e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 5.0067901611328125e-06s
INFO | --- Analysis for coins-openuplabs took 2.890688896179199s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.4677071571350098s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.2508361339569092s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.559226989746094e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 7.152557373046875e-06s
INFO | --- Analysis for CoLChina_sp2000 took 7.1902782917022705s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.06462836265563965s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.24626755714416504s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02055501937866211s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.62396240234375e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for colinda took 2.4509925842285156s
Availability | SPARQL endpoint availability check for CN  2012 took 26.127111673355103s
Availability | VoID file availability check for CN  2012 took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.2619349956512451s
Reputation | Calculation of the PageRank for CN  2012 took 0.020753860473632812s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.647804260253906e-05s
Believability | Calculation of trust value for CN  2012 took 9.298324584960938e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 126.0589509010315s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.363059997558594e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.260852575302124s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020828962326049805s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 7.867813110351562e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 2.8540120124816895s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.1484832763671875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.269683837890625s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 2.9802322387695312e-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 3.2800185680389404s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.1961669921875e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.29454731941223145s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.790855407714844e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 7.62939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.9335997104644775s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.1961669921875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.25296568870544434s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.9325485229492188e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 1.1920928955078125e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.9341671466827393s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.482269287109375e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.25230908393859863s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.021733999252319336s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.1948089599609375e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 6.9141387939453125e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.851083517074585s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.36553239822387695s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.27442312240600586s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 9.5367431640625e-06s
INFO | --- Analysis for CompHistSem took 4.35322642326355s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.294586420059204s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.2698817253112793s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007300376892089844s
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.3909759521484375e-06s
INFO | --- Analysis for comsode-d3-2 took 7.546931028366089s
Availability | SPARQL endpoint availability check for ConceptNet took 5.4836273193359375e-05s
Availability | VoID file availability check for ConceptNet took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.2787454128265381s
Reputation | Calculation of the PageRank for ConceptNet took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.9087066650390625e-05s
Believability | Calculation of trust value for ConceptNet took 7.62939453125e-06s
INFO | --- Analysis for conceptnet took 2.9299476146698s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.38690185546875e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2935221195220947s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.368492126464844e-05s
Believability | Calculation of trust value for 2011 US Congress People took 5.4836273193359375e-06s
INFO | --- Analysis for congresspeople took 3.0054166316986084s
Availability | SPARQL endpoint availability check for MIMO took 0.32169532775878906s
Availability | VoID file availability check for MIMO took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for MIMO took 0.27498292922973633s
Reputation | Calculation of the PageRank for MIMO took 0.02041769027709961s
Interlinking | Calculation of Degree of Connection for MIMO took 1.52587890625e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.049041748046875e-05s
Believability | Calculation of trust value for MIMO took 7.867813110351562e-06s
INFO | --- Analysis for CONNECTED took 3.5804457664489746s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.4345855712890625e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.26816415786743164s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.9129691123962402s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 5.507469177246094e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.2696878910064697s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.0994415283203125e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 8.106231689453125e-06s
INFO | --- Analysis for copac-library-catalogue took 2.9111576080322266s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.291534423828125e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.27253150939941406s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.8371810913085938e-05s
Believability | Calculation of trust value for Copyright Free Music took 7.62939453125e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.7525525093078613s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.410743713378906e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.27130937576293945s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.771087646484375e-05s
Believability | Calculation of trust value for CopyrightTermBank took 7.62939453125e-06s
INFO | --- Analysis for copyrighttermbank took 33.945454120635986s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.8856453895568848s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2490847110748291s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020499467849731445s
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.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.457069396972656e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 8.344650268554688e-06s
INFO | --- Analysis for core took 7.251624584197998s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.6098001003265381s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002682209014892578s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 122.47346925735474s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 1.0966756343841553s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.033851623535156s
Interoperability | New terms check for Corine linked dataset @PSNC took 15.509923696517944s
Versatility | Languages check for Corine linked dataset @PSNC took 300.2446780204773s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 3.3556573390960693s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.2913944721221924s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 11.95453143119812s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.22642064094543457s
License | MR license check for Corine linked dataset @PSNC took 0.5723168849945068s
License | HR license check for Corine linked dataset @PSNC took 300.3132655620575s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.3595108985900879s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.5620718002319336s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.9166762828826904s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.48448944091796875s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.19041824340820312s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.25251007080078125s
Performance | Throughput check for Corine linked dataset @PSNC took 11.78514838218689s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.390975952148438e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.2005176544189453s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.1981031894683838s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4341087341308594s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4588282108306885s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 6.0321619510650635s
Currency | Creation date check for Corine linked dataset @PSNC took 0.515056848526001s
Currency | Modification date check for Corine linked dataset @PSNC took 0.215728759765625s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 158.1976878643036s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.4379551410675049s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.37745118141174316s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.3501298427581787s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 54.0419237613678s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6852405071258545s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.7223849296569824s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.19242382049560547s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 87.20333242416382s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.389009475708008s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 42.04192113876343s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.4141323566436768s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 87.46195006370544s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.7624599933624268s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.5631816387176514s
Security | Sign check for Corine linked dataset @PSNC took 0.6324193477630615s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.453168869018555s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 1.6110129356384277s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021199941635131836s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.409385681152344e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for Corine_linked_dataset took 2308.5848269462585s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.458427429199219e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.7212088108062744s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0208284854888916s
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.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.0994415283203125e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 7.62939453125e-06s
INFO | --- Analysis for corn took 5.114691734313965s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.220008850097656e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2403404712677002s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.02048015594482422s
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.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 2.7418136596679688e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 7.867813110351562e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 4.610373258590698s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.2438507080078125e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.7256739139556885s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0009407997131347656s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.337860107421875e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 8.344650268554688e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 3.269484519958496s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.267692565917969e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.24230551719665527s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.841255187988281e-05s
Believability | Calculation of trust value for Cornetto1.2 took 7.3909759521484375e-06s
INFO | --- Analysis for cornetto took 13.133169889450073s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.18486452102661133s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005304813385009766s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 103.87829613685608s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6096858978271484s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 104.9983139038086s
Interoperability | New terms check for Corporate Body Named Authority List  took 93.58565855026245s
Versatility | Languages check for Corporate Body Named Authority List  took 300.10820722579956s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 1.3860588073730469s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.33042025566101074s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.5344147682189941s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 3.9798638820648193s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.28241467475891113s
License | MR license check for Corporate Body Named Authority List  took 0.24105262756347656s
License | HR license check for Corporate Body Named Authority List  took 300.0840263366699s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.1715984344482422s
Understandability | Number of label check for Corporate Body Named Authority List  took 6.824040651321411s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.22548604011535645s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.11840701103210449s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.17900705337524414s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.1794722080230713s
Performance | Throughput check for Corporate Body Named Authority List  took 10.75715708732605s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 7.390975952148438e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.2117009162902832s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 8.616141319274902s
Interlinking | skos check for Corporate Body Named Authority List  took 0.46715688705444336s
Interlinking | skos check for Corporate Body Named Authority List  took 0.43535327911376953s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.2670149803161621s
Currency | Creation date check for Corporate Body Named Authority List  took 0.4830031394958496s
Currency | Modification date check for Corporate Body Named Authority List  took 0.20112323760986328s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 504.0960764884949s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.18831157684326172s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.2284107208251953s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.15388107299804688s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 26.840689420700073s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.083953380584717s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6227266788482666s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.14635300636291504s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4583990573883s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.511638402938843s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 38.68795919418335s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 11.731900691986084s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.49262261390686s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.034926176071167s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.5082387924194336s
Security | Sign check for Corporate Body Named Authority List  took 0.15825510025024414s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 4.426687240600586s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.6187171936035156s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02817559242248535s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.430511474609375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 9.298324584960938e-06s
INFO | --- Analysis for corporate-body took 15309.562504529953s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.561182975769043s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.2888319492340088s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for CorpusFibonacci took 6.331995010375977s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.291534423828125e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.7209274768829346s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 3.600120544433594e-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 4.631293296813965s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.1287705898284912s
Availability | VoID file availability check for Country Name Authority List took 0.0006003379821777344s
Extra | Recovery of all triples for Country Name Authority List took 104.1325671672821s
Performance | Total latancy measurement for Country Name Authority List took 0.6025199890136719s
Amount of data | Number of triples check for Country Name Authority List took 90.16210389137268s
Interoperability | New terms check for Country Name Authority List took 89.49433445930481s
Versatility | Languages check for Country Name Authority List took 300.1428587436676s
Interpretability | Number of blank nodes check for Country Name Authority List took 1.208925485610962s
Security | Check HTTPS for Country Name Authority List took 0.1922621726989746s
Interpretability | RDF structures check for Country Name Authority List took 0.297410249710083s
Versatility | Serialization formats check for Country Name Authority List took 3.9258968830108643s
Availability | RDF dump link check for Country Name Authority List took 0.2673325538635254s
License | MR license check for Country Name Authority List took 0.2909975051879883s
License | HR license check for Country Name Authority List took 300.1007215976715s
Amount of data | Number of property check for Country Name Authority List took 0.1633741855621338s
Understandability | Number of label check for Country Name Authority List took 5.346923351287842s
Understandability | URI regex check for Country Name Authority List took 0.37326622009277344s
Understandability | Vocabs check for Country Name Authority List took 0.10882067680358887s
Verifiability | Authors check for Country Name Authority List took 0.19750475883483887s
Verifiability | Publishers check for Country Name Authority List took 0.1730358600616455s
Performance | Throughput check for Country Name Authority List took 10.520296812057495s
Amount of data | Check the number of entities for Country Name Authority List took 7.581710815429688e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.12173843383789062s
Interlinking | sameAs chians check for Country Name Authority List took 10.25669240951538s
Interlinking | skos check for Country Name Authority List took 0.25406527519226074s
Interlinking | skos check for Country Name Authority List took 0.22832942008972168s
Timeliness | dataset update frequency check for Country Name Authority List took 0.20810818672180176s
Currency | Creation date check for Country Name Authority List took 0.8916821479797363s
Currency | Modification date check for Country Name Authority List took 0.21315240859985352s
Rep.Conc. | URIs length for Country Name Authority List took 523.0650141239166s
Interoperability | New vocabularies check for Country Name Authority List took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.18438220024108887s
Accuracy | Check Functional Property for Country Name Authority List took 0.19602036476135254s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.16937565803527832s
Accuracy | Check Empty annotation labels for Country Name Authority List took 21.932456016540527s
Accuracy | Check White space in annotation for Country Name Authority List took 3.1603658199310303s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6547861099243164s
Consistency | Disjoint class check for Country Name Authority List took 0.15201497077941895s
Consistency | Check Misplaced properties for Country Name Authority List took 300.4265241622925s
Consistency | Misplaced classes for Country Name Authority List took 8.611053705215454s
Consistency | Check Ontology hijacking for Country Name Authority List took 32.45623970031738s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 9.135894060134888s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.5156569480896s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.041576623916626s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.3778102397918701s
Security | Sign check for Country Name Authority List took 0.15686559677124023s
Availability | Check URIs Dereferenciability for Country Name Authority List took 4.430582523345947s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.6701064109802246s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.022084951400756836s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.6689300537109375e-06s
Believability | Calculation of trust value for Country Name Authority List took 7.62939453125e-06s
INFO | --- Analysis for country-authority-list took 15119.249310016632s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.16788458824157715s
Availability | VoID file availability check for Courts thesaurus took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.7334892749786377s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.0211026668548584s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.842613220214844e-05s
Believability | Calculation of trust value for Courts thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for courts-thesaurus took 4.336353778839111s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.677156925201416s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.2632174491882324s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020812273025512695s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.939338684082031e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 8.821487426757812e-06s
INFO | --- Analysis for Covid-on-the-Web took 6.318771839141846s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.640648126602173s
Availability | VoID file availability check for CPA 2008 took 0.0009725093841552734s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.7125744819641113s
Reputation | Calculation of the PageRank for CPA 2008 took 0.021381139755249023s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.719329833984375e-05s
Believability | Calculation of trust value for CPA 2008 took 5.9604644775390625e-06s
INFO | --- Analysis for cpa-2008 took 127.49073195457458s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.41089510917663574s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005667209625244141s
Extra | Recovery of all triples for Cooperative Patent Classification took 37.96032404899597s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.0367906093597412s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.20585703849792s
Versatility | Languages check for Cooperative Patent Classification took 120.13528060913086s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.28326106071472s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.1887679100036621s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.28055405616760254s
Availability | RDF dump link check for Cooperative Patent Classification took 0.1936502456665039s
License | MR license check for Cooperative Patent Classification took 0.27477216720581055s
License | HR license check for Cooperative Patent Classification took 90.18515753746033s
Amount of data | Number of property check for Cooperative Patent Classification took 0.34705328941345215s
Understandability | Number of label check for Cooperative Patent Classification took 90.20932793617249s
Understandability | URI regex check for Cooperative Patent Classification took 0.5602273941040039s
Understandability | Vocabs check for Cooperative Patent Classification took 0.2517399787902832s
Verifiability | Authors check for Cooperative Patent Classification took 0.2677640914916992s
Verifiability | Publishers check for Cooperative Patent Classification took 0.19400691986083984s
Performance | Throughput check for Cooperative Patent Classification took 10.977579593658447s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.605552673339844e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.17165493965148926s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.17072534561157227s
Interlinking | skos check for Cooperative Patent Classification took 0.18695330619812012s
Interlinking | skos check for Cooperative Patent Classification took 0.2543528079986572s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.30580949783325195s
Currency | Creation date check for Cooperative Patent Classification took 0.4983651638031006s
Currency | Modification date check for Cooperative Patent Classification took 0.3461763858795166s
Rep.Conc. | URIs length for Cooperative Patent Classification took 156.53932809829712s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.22073769569396973s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 18.539891242980957s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9669954776763916s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 5.002729177474976s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.25311875343322754s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.44434523582458s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 20.924756288528442s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.6236393451690674s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.62388610839844s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.8440279960632324s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.29621338844299316s
Security | Sign check for Cooperative Patent Classification took 0.22975754737854004s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.989952564239502s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 1.5732479095458984s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.430511474609375e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 6.9141387939453125e-06s
INFO | --- Analysis for CPC took 1309.3298184871674s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.473816633224487s
Availability | VoID file availability check for CPC 2008 took 0.0009529590606689453s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.277599573135376s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.696846008300781e-05s
Believability | Calculation of trust value for CPC 2008 took 6.67572021484375e-06s
INFO | --- Analysis for cpc-2008 took 127.16919732093811s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.389727115631104s
Availability | VoID file availability check for CPV  2003 took 0.0008168220520019531s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.7793114185333252s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.5299530029296875e-05s
Believability | Calculation of trust value for CPV  2003 took 5.4836273193359375e-06s
INFO | --- Analysis for cpv-2003 took 117.76547741889954s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.322696447372437s
Availability | VoID file availability check for CPV 2008 took 0.0008304119110107422s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.25750017166137695s
Reputation | Calculation of the PageRank for CPV 2008 took 0.02076578140258789s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.9591064453125e-05s
Believability | Calculation of trust value for CPV 2008 took 5.7220458984375e-06s
INFO | --- Analysis for cpv-2008 took 125.07183241844177s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.9635124206543s
Availability | VoID file availability check for crowdsourcing-fb took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 1.3612327575683594s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.023041963577270508s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.601478576660156e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 7.62939453125e-06s
INFO | --- Analysis for crowdsourcing-fb took 537.9993262290955s
Availability | SPARQL endpoint availability check for CRTM took 4.100799560546875e-05s
Availability | VoID file availability check for CRTM took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for CRTM took 0.2563619613647461s
Reputation | Calculation of the PageRank for CRTM took 0.02089691162109375s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.0279159545898438e-05s
Believability | Calculation of trust value for CRTM took 7.3909759521484375e-06s
INFO | --- Analysis for crtm took 4.701775312423706s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.172325134277344e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.6820251941680908s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020418882369995117s
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.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.170967102050781e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 7.3909759521484375e-06s
INFO | --- Analysis for crystal-eye took 4.144040107727051s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.869626760482788s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.2883036136627197s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020660400390625s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 6.198883056640625e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 5.9604644775390625e-06s
INFO | --- Analysis for ctic-public-dataset took 44.597588777542114s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 5.3882598876953125e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.2621471881866455s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.021174907684326172s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0008711814880371094s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.409385681152344e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.3909759521484375e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 3.2453999519348145s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 1.9425256252288818s
Availability | VoID file availability check for CulturaLinkedData took 0.0005412101745605469s
Extra | Recovery of all triples for CulturaLinkedData took 164.19370794296265s
Performance | Total latancy measurement for CulturaLinkedData took 2.299112319946289s
Amount of data | Number of triples check for CulturaLinkedData took 3.4572811126708984s
Interoperability | New terms check for CulturaLinkedData took 2.485344171524048s
Versatility | Languages check for CulturaLinkedData took 60.48193144798279s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.12499737739563s
Interpretability | RDF structures check for CulturaLinkedData took 0.7454991340637207s
Versatility | Serialization formats check for CulturaLinkedData took 0.6688826084136963s
Availability | RDF dump link check for CulturaLinkedData took 0.2983438968658447s
License | MR license check for CulturaLinkedData took 1.1831128597259521s
License | HR license check for CulturaLinkedData took 61.450867891311646s
Amount of data | Number of property check for CulturaLinkedData took 0.10569381713867188s
Understandability | Number of label check for CulturaLinkedData took 0.07934975624084473s
Understandability | URI regex check for CulturaLinkedData took 2.4653232097625732s
Understandability | Vocabs check for CulturaLinkedData took 0.24094414710998535s
Verifiability | Authors check for CulturaLinkedData took 0.417346715927124s
Verifiability | Publishers check for CulturaLinkedData took 2.3411879539489746s
Performance | Throughput check for CulturaLinkedData took 12.140783309936523s
Amount of data | Check the number of entities for CulturaLinkedData took 7.510185241699219e-05s
Verifiability | Contribs. check for CulturaLinkedData took 2.2175586223602295s
Interlinking | sameAs chians check for CulturaLinkedData took 0.07496762275695801s
Interlinking | skos check for CulturaLinkedData took 0.0673980712890625s
Interlinking | skos check for CulturaLinkedData took 0.07276797294616699s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.24190855026245117s
Currency | Creation date check for CulturaLinkedData took 0.27134156227111816s
Currency | Modification date check for CulturaLinkedData took 0.1921863555908203s
Rep.Conc. | URIs length for CulturaLinkedData took 53.48766875267029s
Interoperability | New vocabularies check for CulturaLinkedData took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.2844409942626953s
Accuracy | Check Functional Property for CulturaLinkedData took 0.15888667106628418s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.17239761352539062s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 49.49106454849243s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.620485782623291s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.3034956455230713s
Consistency | Disjoint class check for CulturaLinkedData took 0.07178473472595215s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.604932069778442s
Consistency | Misplaced classes for CulturaLinkedData took 4.097047805786133s
Consistency | Check Ontology hijacking for CulturaLinkedData took 28.944284200668335s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.418931245803833s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 12.097808599472046s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3793995380401611s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 1.8526651859283447s
Security | Sign check for CulturaLinkedData took 1.027219295501709s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 12.153355121612549s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.8120708465576172s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.6689300537109375e-06s
Believability | Calculation of trust value for CulturaLinkedData took 7.62939453125e-06s
INFO | --- Analysis for culturalinkeddata took 620.9962694644928s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.21776819229125977s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2552320957183838s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0008604526519775391s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-ares-or took 5.582977533340454s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11142754554748535s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0008070468902587891s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.25711989402770996s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020334482192993164s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.504753112792969e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.76837158203125e-06s
INFO | --- Analysis for cz-ares-rzp took 2.6506998538970947s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.10845398902893066s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.28063201904296875s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.409385681152344e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 4.76837158203125e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.270231008529663s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10840463638305664s
Availability | VoID file availability check for Integrated pollution registry took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.2531156539916992s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.504753112792969e-05s
Believability | Calculation of trust value for Integrated pollution registry took 4.5299530029296875e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.7684895992279053s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11211442947387695s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.6872992515563965s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020186901092529297s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.409385681152344e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 5.0067901611328125e-06s
INFO | --- Analysis for cz-contracts took 3.1131324768066406s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 6.794929504394531e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.2805056571960449s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.9087066650390625e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-courts took 2.9098939895629883s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.10472226142883301s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2784402370452881s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.5762786865234375e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-bans took 4.9455554485321045s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.11187386512756348s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.2566845417022705s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.361701965332031e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.637259006500244s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.10851669311523438s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.249267578125s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.4332275390625e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.245208740234375e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7279703617095947s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10851216316223145s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.25589418411254883s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.100799560546875e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.7296547889709473s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.10904693603515625s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2509028911590576s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.0994415283203125e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 4.291534423828125e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.639528751373291s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 10.219327688217163s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0009613037109375s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.25395894050598145s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020960092544555664s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.029273986816406e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 6.4373016357421875e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 22.90219259262085s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 10.109477996826172s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2698171138763428s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.218650817871094e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 5.0067901611328125e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 22.868269443511963s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 1.0676438808441162s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.6931328773498535s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02101755142211914s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-average-salaries took 4.383371114730835s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3945624828338623s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.2765936851501465s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.021482467651367188s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.267692565917969e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.237974166870117s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3799140453338623s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.26457905769348145s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.021036386489868164s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0009777545928955078s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.1961669921875e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.273604393005371s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3981435298919678s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2697415351867676s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.305673599243164s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.4035370349884033s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2523188591003418s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.2847542762756348s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.5017266273498535s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007679462432861328s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2652287483215332s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.4332275390625e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-regions took 3.0564515590667725s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.4096987247467041s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.27454566955566406s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020959138870239258s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.349501609802246s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.3773033618927002s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2806131839752197s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.323178291320801s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.3733088970184326s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.28482651710510254s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.814697265625e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.261740207672119s
Availability | SPARQL endpoint availability check for ATC groups took 0.10900759696960449s
Availability | VoID file availability check for ATC groups took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for ATC groups took 0.28224635124206543s
Reputation | Calculation of the PageRank for ATC groups took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.05718994140625e-05s
Believability | Calculation of trust value for ATC groups took 1.3113021850585938e-05s
INFO | --- Analysis for cz-eh-1-atc took 2.741525173187256s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10463786125183105s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2639782428741455s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020731449127197266s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 4.029273986816406e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.9604644775390625e-06s
INFO | --- Analysis for cz-fulfillments took 2.6366941928863525s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.039473533630371094s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.23396515846252441s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.935264587402344e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ic took 3.11848521232605s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.15586328506469727s
Availability | VoID file availability check for List of Czech data boxes took 0.0005991458892822266s
Extra | Recovery of all triples for List of Czech data boxes took 236.10437417030334s
Performance | Total latancy measurement for List of Czech data boxes took 0.5938184261322021s
Amount of data | Number of triples check for List of Czech data boxes took 73.02604556083679s
Interoperability | New terms check for List of Czech data boxes took 18.69126272201538s
Versatility | Languages check for List of Czech data boxes took 300.1574547290802s
Interpretability | Number of blank nodes check for List of Czech data boxes took 4.445031642913818s
Interpretability | RDF structures check for List of Czech data boxes took 0.25220537185668945s
Versatility | Serialization formats check for List of Czech data boxes took 0.8861985206604004s
Availability | RDF dump link check for List of Czech data boxes took 36.445523500442505s
License | MR license check for List of Czech data boxes took 0.4566538333892822s
License | HR license check for List of Czech data boxes took 300.1387972831726s
Amount of data | Number of property check for List of Czech data boxes took 0.29115915298461914s
Understandability | Number of label check for List of Czech data boxes took 3.094456434249878s
Understandability | URI regex check for List of Czech data boxes took 0.533294677734375s
Understandability | Vocabs check for List of Czech data boxes took 0.2718539237976074s
Verifiability | Authors check for List of Czech data boxes took 0.43858814239501953s
Verifiability | Publishers check for List of Czech data boxes took 0.1491239070892334s
Performance | Throughput check for List of Czech data boxes took 10.465532541275024s
Amount of data | Check the number of entities for List of Czech data boxes took 2.9943435192108154s
Verifiability | Contribs. check for List of Czech data boxes took 0.9870965480804443s
Interlinking | sameAs chians check for List of Czech data boxes took 1.7258293628692627s
Interlinking | skos check for List of Czech data boxes took 0.29964613914489746s
Interlinking | skos check for List of Czech data boxes took 0.11214494705200195s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.9238767623901367s
Currency | Creation date check for List of Czech data boxes took 2.646267890930176s
Currency | Modification date check for List of Czech data boxes took 0.5934872627258301s
Rep.Conc. | URIs length for List of Czech data boxes took 200.7954716682434s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.48258519172668457s
Accuracy | Check Functional Property for List of Czech data boxes took 0.1662747859954834s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.1563708782196045s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 95.04067778587341s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.1352880001068115s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.6127841472625732s
Consistency | Disjoint class check for List of Czech data boxes took 0.18213891983032227s
Consistency | Check Misplaced properties for List of Czech data boxes took 102.27525210380554s
Consistency | Misplaced classes for List of Czech data boxes took 7.794841527938843s
Consistency | Check Ontology hijacking for List of Czech data boxes took 74.75400900840759s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.4562034606933594s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 93.72887587547302s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.6691508293151855s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.9106111526489258s
Security | Sign check for List of Czech data boxes took 0.16267776489257812s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 489.7571704387665s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 1.4633452892303467s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0009479522705078125s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 5.53131103515625e-05s
Believability | Calculation of trust value for List of Czech data boxes took 5.4836273193359375e-06s
INFO | --- Analysis for cz-list-of-databoxes took 2883.939195394516s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12387275695800781s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006721019744873047s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 246.56372237205505s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5709280967712402s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 28.498120307922363s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 15.187664270401001s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.12878799438477s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.0113396644592285s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1963796615600586s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.9250037670135498s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 34.76744103431702s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3464844226837158s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1811525821686s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2859330177307129s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.5862724781036377s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.36158013343811035s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17740511894226074s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2185378074645996s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1912243366241455s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.366826295852661s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0635552406311035s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.9141807556152344s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0256404876708984s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2842710018157959s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10069394111633301s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6361572742462158s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7573630809783936s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3379523754119873s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 194.38294196128845s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.46804308891296387s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1454613208770752s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.16658973693847656s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 87.6330783367157s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0981035232543945s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.7302889823913574s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.09947729110717773s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 97.3574607372284s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.678461790084839s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 75.70043563842773s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.47316575050354s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 82.33972477912903s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6788558959960938s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.47130370140075684s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15089178085327148s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 533.2843861579895s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.1619460582733154s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.020945072174072266s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.100799560546875e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.4836273193359375e-06s
INFO | --- Analysis for cz-nace took 2467.575315952301s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.29659080505371094s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005953311920166016s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 177.17524313926697s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8141264915466309s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.294309139251709s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5390989780426025s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 38.2750678062439s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.46720170974731445s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15593290328979492s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.250761270523071s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2956571578979492s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3621392250061035s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5662431716918945s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15385150909423828s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.600848913192749s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.32237744331359863s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1634066104888916s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24483609199523926s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.29796385765075684s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 11.042871713638306s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.00011229515075683594s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15314817428588867s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.21335601806640625s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3269829750061035s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16501235961914062s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6094372272491455s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3964824676513672s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.34816718101501465s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 56.71128797531128s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16530346870422363s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15190792083740234s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16593599319458008s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 41.140934467315674s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.3999581336975098s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6913163661956787s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17619681358337402s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.975069522857666s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.250742435455322s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 96.01383471488953s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7717809677124023s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.175250768661499s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.4830946922302246s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.22108817100524902s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.42142796516418457s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 981.0427074432373s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7306849956512451s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.021926403045654297s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.1920928955078125e-06s
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 75680.49180316925s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.21800994873046875s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.24934983253479004s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.8623809814453125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 5.245208740234375e-06s
INFO | --- Analysis for cz-orders took 4.12234091758728s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.18254923820495605s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0006029605865478516s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 239.53351879119873s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5275323390960693s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 53.278958320617676s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 17.2579505443573s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.18300342559814s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 3.4446611404418945s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.2347118854522705s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 1.2617969512939453s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 35.624433755874634s
License | MR license check for Institutions of public power of the Czech Republic took 0.36383605003356934s
License | HR license check for Institutions of public power of the Czech Republic took 300.1614124774933s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.2990758419036865s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 5.201112985610962s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.38979530334472656s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.2679574489593506s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.19373345375061035s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.22086763381958008s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.305317401885986s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.0902984142303467s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 1.0816559791564941s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 1.9998719692230225s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.23323941230773926s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.1225743293762207s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.47156405448913574s
Currency | Creation date check for Institutions of public power of the Czech Republic took 4.1690545082092285s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.3851499557495117s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 198.7841935157776s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.5560817718505859s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.15989995002746582s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.14876222610473633s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 104.80427527427673s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0867040157318115s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.684912919998169s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.1254880428314209s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 98.58573007583618s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 8.103637456893921s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 81.15421295166016s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.3598952293395996s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 79.34871649742126s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6945369243621826s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.9438374042510986s
Security | Sign check for Institutions of public power of the Czech Republic took 0.14805817604064941s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 12.426329135894775s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.9913604259490967s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.02102828025817871s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.602836608886719e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-ovm took 2364.792922258377s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.10647988319396973s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.25343871116638184s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.02078700065612793s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 4.38690185546875e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ovm-agendas took 4.84894061088562s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 20.060392141342163s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.2385523319244385s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0008363723754882812s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.748603820800781e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-ruian took 114.37667226791382s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7441420555114746s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.27257776260375977s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0008559226989746094s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.486343383789062e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 4.721948623657227s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.5062346458435059s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.2611360549926758s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.9909238815307617s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.47738218307495117s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.2432570457458496s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 2.8371810913085938e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 5.0067901611328125e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.5030148029327393s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10914158821105957s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.27520203590393066s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.62396240234375e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.7527849674224854s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10440325736999512s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2691009044647217s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.457069396972656e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.6856768131256104s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11078572273254395s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0007646083831787109s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2642858028411865s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.02161431312561035s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.62396240234375e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.1444091796875e-05s
INFO | --- Analysis for cz-sidc-drugs took 2.8459584712982178s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.11327290534973145s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005736351013183594s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 240.0262155532837s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.543907642364502s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 46.260406255722046s
Interoperability | New terms check for Summary types of Czech institutions of public power took 21.060604333877563s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.15623712539673s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 13.194756031036377s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.2922825813293457s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 4.433196544647217s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 35.00120186805725s
License | MR license check for Summary types of Czech institutions of public power took 0.1122124195098877s
License | HR license check for Summary types of Czech institutions of public power took 300.10321855545044s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.617072582244873s
Understandability | Number of label check for Summary types of Czech institutions of public power took 19.772457599639893s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.25557613372802734s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.20806360244750977s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.6036229133605957s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.3296492099761963s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.390509605407715s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.0284883975982666s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 3.0370712280273438s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 3.394517421722412s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.888206958770752s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.10076498985290527s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 1.5164790153503418s
Currency | Creation date check for Summary types of Czech institutions of public power took 2.7707974910736084s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.43384814262390137s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 231.82879614830017s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.5769917964935303s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.12179946899414062s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.11231732368469238s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 127.38901233673096s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.096494436264038s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6480391025543213s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.1209721565246582s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 111.00697040557861s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 8.418485879898071s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 77.05319142341614s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.3513844013214111s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 93.06963753700256s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.6854827404022217s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 1.9711380004882812s
Security | Sign check for Summary types of Czech institutions of public power took 0.12242531776428223s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 12.754748344421387s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.241370677947998s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021169424057006836s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.291534423828125e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.7220458984375e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2560.0217707157135s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.11185646057128906s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0008068084716796875s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.24577784538269043s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02132868766784668s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.457069396972656e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 3.563995599746704s
Availability | SPARQL endpoint availability check for State funding providers took 0.09509897232055664s
Availability | VoID file availability check for State funding providers took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for State funding providers took 0.24458622932434082s
Reputation | Calculation of the PageRank for State funding providers took 0.020781517028808594s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.7670135498046875e-05s
Believability | Calculation of trust value for State funding providers took 5.7220458984375e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.52089786529541s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.09699201583862305s
Availability | VoID file availability check for Organizations active in R&D took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.7264385223388672s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.910064697265625e-05s
Believability | Calculation of trust value for Organizations active in R&D took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-organizations took 3.305452823638916s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.1092534065246582s
Availability | VoID file availability check for R&D Programmes took 0.0007965564727783203s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2595348358154297s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.6253204345703125e-05s
Believability | Calculation of trust value for R&D Programmes took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-programmes took 3.2252564430236816s
Availability | SPARQL endpoint availability check for R&D Projects took 0.10864591598510742s
Availability | VoID file availability check for R&D Projects took 0.0011682510375976562s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.275662899017334s
Reputation | Calculation of the PageRank for R&D Projects took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0008165836334228516s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.00543212890625e-05s
Believability | Calculation of trust value for R&D Projects took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-projects took 3.174076557159424s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10863184928894043s
Availability | VoID file availability check for Institutional research plans took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.26383161544799805s
Reputation | Calculation of the PageRank for Institutional research plans took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0009264945983886719s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.458427429199219e-05s
Believability | Calculation of trust value for Institutional research plans took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.7100367546081543s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11115717887878418s
Availability | VoID file availability check for Results of R&D took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.27404069900512695s
Reputation | Calculation of the PageRank for Results of R&D took 0.020429611206054688s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.790855407714844e-05s
Believability | Calculation of trust value for Results of R&D took 5.7220458984375e-06s
INFO | --- Analysis for cz-vavai-results took 2.7722673416137695s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.10496902465820312s
Availability | VoID file availability check for Tenders in R&D took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.27675366401672363s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.743171691894531e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.7520878314971924s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.3392181396484375e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.2554323673248291s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.8623809814453125e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 6.67572021484375e-06s
INFO | --- Analysis for czech_addresses took 4.297139406204224s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.5758464336395264s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.262631893157959s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.3589859008789062e-05s
INFO | --- Analysis for DanteLatinLoanwords took 3.888162136077881s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.384476900100708s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006113052368164062s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 149.90961575508118s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0603320598602295s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 16.74697184562683s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 3.0338919162750244s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.34036922454834s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.24944233894348145s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.11968469619750977s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.5403294563293457s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.29189062118530273s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.22485113143920898s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.255767822265625s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 53.87995886802673s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.2355365753173828s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 0.9034008979797363s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4439389705657959s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.24077415466308594s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.22847557067871094s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.2370748519897461s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.675888299942017s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.557868957519531e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.23553967475891113s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.6062126159667969s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 2.6034905910491943s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.7376708984375s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.23581814765930176s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 2.825676679611206s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 4.535362958908081s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 79.79462432861328s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.22511625289916992s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.4296128749847412s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.4332423210144043s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 44.20465707778931s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2804620265960693s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.630031108856201s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.39355897903442383s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.443100929260254s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.746092319488525s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 50.50088286399841s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4249451160430908s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.21110987663269s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.852229356765747s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2549259662628174s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.22438836097717285s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 9.854814767837524s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.8427431583404541s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021589994430541992s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.0001583099365234375s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 2.1457672119140625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 8.58306884765625e-06s
INFO | --- Analysis for data-bnf-fr took 804.7952702045441s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.13479089736938477s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005230903625488281s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.6563220024108887s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.3104250431060791s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 4.447141885757446s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.4697983264923096s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.08595442771911621s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.6082363128662109s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.03665971755981445s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.10494756698608398s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.0993349552154541s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.08842325210571289s
License | MR license check for Open Data from the Italian National Research Council took 0.09929847717285156s
License | HR license check for Open Data from the Italian National Research Council took 11.709013223648071s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.09536170959472656s
Understandability | Number of label check for Open Data from the Italian National Research Council took 3.8491265773773193s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.18425488471984863s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.09462809562683105s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.09415841102600098s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.08896517753601074s
Performance | Throughput check for Open Data from the Italian National Research Council took 10.410574436187744s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 8.058547973632812e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.0892949104309082s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.0918583869934082s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.09064698219299316s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.05467104911804199s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.09232807159423828s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.1869187355041504s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.1921985149383545s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 12.467885255813599s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.09106659889221191s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.09130048751831055s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.08954739570617676s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.4120464324951172s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.032529354095458984s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.02757549285888672s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.08666825294494629s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 10.067875623703003s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.19519495964050293s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.5426201820373535s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.2616724967956543s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 11.723812103271484s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.03235602378845215s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.11237859725952148s
Security | Sign check for Open Data from the Italian National Research Council took 0.09171128273010254s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 646.0938079357147s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.46340036392211914s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.0210263729095459s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.628036499023438e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.9604644775390625e-06s
INFO | --- Analysis for data-cnr-it took 747.8285629749298s
Availability | SPARQL endpoint availability check for Data.gov took 1.4399867057800293s
Availability | VoID file availability check for Data.gov took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Data.gov took 0.2555556297302246s
Reputation | Calculation of the PageRank for Data.gov took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Data.gov took 2.9802322387695312e-05s
Believability | Calculation of trust value for Data.gov took 5.7220458984375e-06s
INFO | --- Analysis for data-gov took 18.958629846572876s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.43070030212402344s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.2631795406341553s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.818771362304688e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 5.9604644775390625e-06s
INFO | --- Analysis for data-gov-ie took 3.736232042312622s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 5.7220458984375e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.250638484954834s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007297992706298828s
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 5.0067901611328125e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.9539308547973633s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.97416591644287s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.7365713119506836s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.961822509765625e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.0251998901367188e-05s
INFO | --- Analysis for data-hnm-hu took 159.07336854934692s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.16868996620178223s
Availability | VoID file availability check for Climb Dataincubator took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.25491762161254883s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.414817810058594e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.867813110351562e-06s
INFO | --- Analysis for data-incubator-climb took 2.978987693786621s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.482269287109375e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.27069854736328125s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.036064147949219e-05s
Believability | Calculation of trust value for Discogs in RDF took 9.059906005859375e-06s
INFO | --- Analysis for data-incubator-discogs took 7.658408880233765s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.06003260612487793s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.2716526985168457s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.7220458984375e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 5.245208740234375e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.675792694091797s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.05699634552001953s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.26691150665283203s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.7738037109375e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-moseley took 9.039869546890259s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.050661325454711914s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.25519609451293945s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.02130413055419922s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.036064147949219e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.462477445602417s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.8117129802703857s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.2614419460296631s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020432472229003906s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007376670837402344s
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 5.9604644775390625e-06s
INFO | --- Analysis for data-incubator-nasa took 7.6496312618255615s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.06517958641052246s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0003745555877685547s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.24989843368530273s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 8.082389831542969e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 8.58306884765625e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.472515106201172s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.05968904495239258s
Availability | VoID file availability check for Pokedex data in RDF took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2699549198150635s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.083747863769531e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.092414140701294s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.055207014083862305s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.2662205696105957s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020296812057495117s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.012222290039062e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.4189248085021973s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.5107717514038086s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006651878356933594s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 71.3468029499054s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.3264601230621338s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 0.26935482025146484s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5352258682250977s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 10.020551919937134s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 0.2984492778778076s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.14713168144226074s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.31758761405944824s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.35018062591552734s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.28400301933288574s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.3081393241882324s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 3.078254222869873s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.27133846282958984s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 0.4395906925201416s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.57318115234375s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.3076589107513428s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.31406164169311523s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.30005788803100586s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 10.63103437423706s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.009506225585938e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.29491448402404785s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.2895827293395996s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.3198397159576416s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2948110103607178s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.29697299003601074s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.5999655723571777s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.6238329410552979s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 54.81313872337341s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.2956051826477051s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.2939121723175049s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.28360605239868164s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 35.38227963447571s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.1849124431610107s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.2711832523345947s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.8117327690124512s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 18.388014793395996s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.5972671508789062s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.0001461505889892578s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.4431636333465576s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.3005027770996094s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 1894.3713462352753s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 1.2660057544708252s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.021295547485351562s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 1.430511474609375e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 7.3909759521484375e-06s
INFO | --- Analysis for data-open-ac-uk took 2195.124216079712s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8378748893737793s
Availability | VoID file availability check for Persée in RDF took 0.0006260871887207031s
Extra | Recovery of all triples for Persée in RDF took 2.0837771892547607s
Performance | Total latancy measurement for Persée in RDF took 0.6000723838806152s
Amount of data | Number of triples check for Persée in RDF took 7.56258225440979s
Interoperability | New terms check for Persée in RDF took 1.7776007652282715s
Versatility | Languages check for Persée in RDF took 120.53973913192749s
Interpretability | Number of blank nodes check for Persée in RDF took 0.659602165222168s
Interpretability | RDF structures check for Persée in RDF took 0.969940185546875s
Versatility | Serialization formats check for Persée in RDF took 0.8980731964111328s
Availability | RDF dump link check for Persée in RDF took 0.2923316955566406s
License | MR license check for Persée in RDF took 1.4072959423065186s
License | HR license check for Persée in RDF took 37.299851179122925s
Amount of data | Number of property check for Persée in RDF took 0.1536092758178711s
Understandability | Number of label check for Persée in RDF took 1.87070894241333s
Understandability | URI regex check for Persée in RDF took 0.8797826766967773s
Understandability | Vocabs check for Persée in RDF took 0.41826677322387695s
Verifiability | Authors check for Persée in RDF took 0.14267468452453613s
Verifiability | Publishers check for Persée in RDF took 0.13270068168640137s
Performance | Throughput check for Persée in RDF took 10.741510391235352s
Amount of data | Check the number of entities for Persée in RDF took 0.00010991096496582031s
Verifiability | Contribs. check for Persée in RDF took 0.15051054954528809s
Interlinking | sameAs chians check for Persée in RDF took 0.16017532348632812s
Interlinking | skos check for Persée in RDF took 0.6953554153442383s
Interlinking | skos check for Persée in RDF took 0.1476142406463623s
Timeliness | dataset update frequency check for Persée in RDF took 0.6695961952209473s
Currency | Creation date check for Persée in RDF took 0.5012478828430176s
Currency | Modification date check for Persée in RDF took 0.29923415184020996s
Rep.Conc. | URIs length for Persée in RDF took 3.672438144683838s
Interoperability | New vocabularies check for Persée in RDF took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.14595913887023926s
Accuracy | Check Functional Property for Persée in RDF took 0.13214945793151855s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.1354372501373291s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.869694709777832s
Accuracy | Check White space in annotation for Persée in RDF took 0.03829169273376465s
Accuracy | Check Datatype consistency for Persée in RDF took 0.028224945068359375s
Consistency | Disjoint class check for Persée in RDF took 0.2785799503326416s
Consistency | Check Misplaced properties for Persée in RDF took 2.6628265380859375s
Consistency | Misplaced classes for Persée in RDF took 0.22396039962768555s
Consistency | Check Ontology hijacking for Persée in RDF took 1.8200433254241943s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.192305564880371s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.705113172531128s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03662252426147461s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.13331317901611328s
Security | Sign check for Persée in RDF took 0.7453312873840332s
Availability | Check URIs Dereferenciability for Persée in RDF took 1367.2258124351501s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.8341917991638184s
Reputation | Calculation of the PageRank for Persée in RDF took 0.021064281463623047s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00011706352233886719s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.430511474609375e-06s
Believability | Calculation of trust value for Persée in RDF took 7.867813110351562e-06s
INFO | --- Analysis for data-persee-fr took 1618.21439743042s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 5.054473876953125e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.27135419845581055s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.1948089599609375e-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 4.698165416717529s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.5377070903778076s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.2589995861053467s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.0001246929168701172s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 6.67572021484375e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.447936058044434s
Availability | SPARQL endpoint availability check for Open Data Web took 0.2783496379852295s
Availability | VoID file availability check for Open Data Web took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.24029183387756348s
Reputation | Calculation of the PageRank for Open Data Web took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.0517578125e-05s
Believability | Calculation of trust value for Open Data Web took 6.4373016357421875e-06s
INFO | --- Analysis for data.odw.tw took 2.6809542179107666s
Availability | SPARQL endpoint availability check for DataFAQs took 4.863739013671875e-05s
Availability | VoID file availability check for DataFAQs took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.2701253890991211s
Reputation | Calculation of the PageRank for DataFAQs took 0.021318674087524414s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.8623809814453125e-05s
Believability | Calculation of trust value for DataFAQs took 7.62939453125e-06s
INFO | --- Analysis for datafaqs took 2.9160993099212646s
Availability | SPARQL endpoint availability check for datahub took 7.128715515136719e-05s
Availability | VoID file availability check for datahub took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for datahub took 0.27486276626586914s
Reputation | Calculation of the PageRank for datahub took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for datahub took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for datahub took 4.696846008300781e-05s
Believability | Calculation of trust value for datahub took 7.867813110351562e-06s
INFO | --- Analysis for datahub took 3.5818750858306885s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 5.30702543258667s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.2574582099914551s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.0517578125e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.2636184692382812e-05s
INFO | --- Analysis for datahub-kr-datamap took 15.333809614181519s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.4923884868621826s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.24720358848571777s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.818771362304688e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.867813110351562e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 4.985859632492065s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.403499364852905s
Availability | VoID file availability check for datos-artium-org took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.8802950382232666s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00010991096496582031s
Believability | Calculation of trust value for datos-artium-org took 1.239776611328125e-05s
INFO | --- Analysis for datos-artium-org took 166.57716250419617s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8972008228302002s
Availability | VoID file availability check for Datos.bcn.cl took 0.0003807544708251953s
Extra | Recovery of all triples for Datos.bcn.cl took 58.76092314720154s
Performance | Total latancy measurement for Datos.bcn.cl took 6.2211809158325195s
Amount of data | Number of triples check for Datos.bcn.cl took 3.7108139991760254s
Interoperability | New terms check for Datos.bcn.cl took 3.597928762435913s
Versatility | Languages check for Datos.bcn.cl took 301.0951900482178s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 3.3140790462493896s
Security | Check HTTPS for Datos.bcn.cl took 0.7250840663909912s
Interpretability | RDF structures check for Datos.bcn.cl took 1.3144099712371826s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2920513153076172s
Availability | RDF dump link check for Datos.bcn.cl took 1.2366650104522705s
License | MR license check for Datos.bcn.cl took 1.3339264392852783s
License | HR license check for Datos.bcn.cl took 18.256473302841187s
Amount of data | Number of property check for Datos.bcn.cl took 1.274904489517212s
Understandability | Number of label check for Datos.bcn.cl took 1.4414770603179932s
Understandability | URI regex check for Datos.bcn.cl took 2.475304365158081s
Understandability | Vocabs check for Datos.bcn.cl took 1.2232732772827148s
Verifiability | Authors check for Datos.bcn.cl took 1.2578611373901367s
Verifiability | Publishers check for Datos.bcn.cl took 1.2390413284301758s
Performance | Throughput check for Datos.bcn.cl took 12.347592115402222s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.176399230957031e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2040328979492188s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2450065612792969s
Interlinking | skos check for Datos.bcn.cl took 1.2270333766937256s
Interlinking | skos check for Datos.bcn.cl took 1.2542288303375244s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2563683986663818s
Currency | Creation date check for Datos.bcn.cl took 2.4575345516204834s
Currency | Modification date check for Datos.bcn.cl took 1.2132556438446045s
Rep.Conc. | URIs length for Datos.bcn.cl took 38.21442174911499s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2424070835113525s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.2174174785614014s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.2386474609375s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 22.797961950302124s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.23923897743225098s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.27573275566101074s
Consistency | Disjoint class check for Datos.bcn.cl took 1.2386589050292969s
Consistency | Check Misplaced properties for Datos.bcn.cl took 6.296480894088745s
Consistency | Misplaced classes for Datos.bcn.cl took 2.0789504051208496s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 23.605225801467896s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.2265000343322754s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 6.311118125915527s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.29498887062072754s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.500636339187622s
Security | Sign check for Datos.bcn.cl took 1.2260465621948242s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 8936.375601768494s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.1622297763824463s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02121710777282715s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 8.177757263183594e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.6689300537109375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 6.4373016357421875e-06s
INFO | --- Analysis for datos-bcn-cl took 9793.566148042679s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.44002485275268555s
Availability | VoID file availability check for datos.bne.es took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.698606014251709s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011086463928222656s
Believability | Calculation of trust value for datos.bne.es took 1.0967254638671875e-05s
INFO | --- Analysis for datos-bne-es took 5.895731210708618s
Availability | SPARQL endpoint availability check for dbacademic took 0.1694636344909668s
Availability | VoID file availability check for dbacademic took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for dbacademic took 0.2557101249694824s
Reputation | Calculation of the PageRank for dbacademic took 0.02020096778869629s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for dbacademic took 2.8133392333984375e-05s
Believability | Calculation of trust value for dbacademic took 4.76837158203125e-06s
INFO | --- Analysis for dbacademic took 2.9534974098205566s
Availability | SPARQL endpoint availability check for DBkWik took 0.23189377784729004s
Availability | VoID file availability check for DBkWik took 0.0007054805755615234s
Extra | Recovery of all triples for DBkWik took 13.093074798583984s
Performance | Total latancy measurement for DBkWik took 0.43663859367370605s
Amount of data | Number of triples check for DBkWik took 11.387825965881348s
Interoperability | New terms check for DBkWik took 2.0970418453216553s
Versatility | Languages check for DBkWik took 137.47159671783447s
Interpretability | Number of blank nodes check for DBkWik took 1.1456406116485596s
Interpretability | RDF structures check for DBkWik took 0.21261930465698242s
Versatility | Serialization formats check for DBkWik took 0.2909414768218994s
Availability | RDF dump link check for DBkWik took 2.8808705806732178s
License | MR license check for DBkWik took 0.507533073425293s
License | HR license check for DBkWik took 61.93797302246094s
Amount of data | Number of property check for DBkWik took 0.12530016899108887s
Understandability | Number of label check for DBkWik took 2.110970973968506s
Understandability | URI regex check for DBkWik took 0.2879204750061035s
Understandability | Vocabs check for DBkWik took 0.11774444580078125s
Verifiability | Authors check for DBkWik took 0.12461590766906738s
Verifiability | Publishers check for DBkWik took 0.09828567504882812s
Performance | Throughput check for DBkWik took 10.48095178604126s
Amount of data | Check the number of entities for DBkWik took 3.457069396972656e-05s
Verifiability | Contribs. check for DBkWik took 0.1043388843536377s
Interlinking | sameAs chians check for DBkWik took 0.40203237533569336s
Interlinking | skos check for DBkWik took 0.46106743812561035s
Interlinking | skos check for DBkWik took 0.08404421806335449s
Timeliness | dataset update frequency check for DBkWik took 0.20255136489868164s
Currency | Creation date check for DBkWik took 0.5049221515655518s
Currency | Modification date check for DBkWik took 0.19443535804748535s
Rep.Conc. | URIs length for DBkWik took 14.11828327178955s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.10975027084350586s
Accuracy | Check Functional Property for DBkWik took 0.30255889892578125s
Accuracy | Check Inverse Functional Property for DBkWik took 0.26805663108825684s
Accuracy | Check Empty annotation labels for DBkWik took 1.4717597961425781s
Accuracy | Check White space in annotation for DBkWik took 0.024035215377807617s
Accuracy | Check Datatype consistency for DBkWik took 0.02756643295288086s
Consistency | Disjoint class check for DBkWik took 0.11665177345275879s
Consistency | Check Misplaced properties for DBkWik took 13.88269567489624s
Consistency | Misplaced classes for DBkWik took 0.6797192096710205s
Consistency | Check Ontology hijacking for DBkWik took 1.823012351989746s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.158107042312622s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.600278854370117s
Conciseness | Check Extensional conciseness for DBkWik took 0.03260946273803711s
Conciseness | Check Intensional conciseness for DBkWik took 1.5800387859344482s
Security | Sign check for DBkWik took 0.2663609981536865s
Availability | Check URIs Dereferenciability for DBkWik took 11.957918405532837s
Completeness | Calculation of interlinking completeness for DBkWik took 0.7831461429595947s
Reputation | Calculation of the PageRank for DBkWik took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.700920104980469e-05s
Believability | Calculation of trust value for DBkWik took 7.867813110351562e-06s
INFO | --- Analysis for dbkwik took 1450.6732637882233s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 5.125999450683594e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.26720190048217773s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.000110626220703125s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 45.226574659347534s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.4869821071624756s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0006432533264160156s
Extra | Recovery of all triples for dblp Knowledge Graph took 71.42305874824524s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7356152534484863s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.15098810195922852s
Interoperability | New terms check for dblp Knowledge Graph took 1.717186689376831s
Versatility | Languages check for dblp Knowledge Graph took 30.21857213973999s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.1686017513275146s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.1876058578491211s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.14924979209899902s
Availability | RDF dump link check for dblp Knowledge Graph took 0.12674570083618164s
License | MR license check for dblp Knowledge Graph took 0.19930315017700195s
License | HR license check for dblp Knowledge Graph took 30.157312393188477s
Amount of data | Number of property check for dblp Knowledge Graph took 0.15526032447814941s
Understandability | Number of label check for dblp Knowledge Graph took 0.5532982349395752s
Understandability | URI regex check for dblp Knowledge Graph took 0.31261563301086426s
Understandability | Vocabs check for dblp Knowledge Graph took 0.1764681339263916s
Verifiability | Authors check for dblp Knowledge Graph took 0.12868762016296387s
Verifiability | Publishers check for dblp Knowledge Graph took 0.15128660202026367s
Performance | Throughput check for dblp Knowledge Graph took 11.220456600189209s
Amount of data | Check the number of entities for dblp Knowledge Graph took 0.00013136863708496094s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.15863585472106934s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.21889781951904297s
Interlinking | skos check for dblp Knowledge Graph took 0.15167665481567383s
Interlinking | skos check for dblp Knowledge Graph took 0.12662744522094727s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.15746784210205078s
Currency | Creation date check for dblp Knowledge Graph took 0.3173685073852539s
Currency | Modification date check for dblp Knowledge Graph took 0.28839540481567383s
Rep.Conc. | URIs length for dblp Knowledge Graph took 24.502939701080322s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.15640473365783691s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.14632630348205566s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.14652800559997559s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 21.84896969795227s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.086991786956787s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.14901399612426758s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.31787967681884766s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 18.713892936706543s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 1.3567028045654297s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 0.00014662742614746094s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.16816449165344238s
Security | Sign check for dblp Knowledge Graph took 0.17127251625061035s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.41397690773010254s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020785093307495117s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for dblp-kg took 285.87691354751587s
Availability | SPARQL endpoint availability check for dbnary took 0.26929688453674316s
Availability | VoID file availability check for dbnary took 0.0004634857177734375s
Extra | Recovery of all triples for dbnary took 1.7607007026672363s
Performance | Total latancy measurement for dbnary took 0.36304473876953125s
Amount of data | Number of triples check for dbnary took 3.9171485900878906s
Interoperability | New terms check for dbnary took 3.6152236461639404s
Versatility | Languages check for dbnary took 61.699156522750854s
Interpretability | Number of blank nodes check for dbnary took 0.7423911094665527s
Security | Check HTTPS for dbnary took 0.19309544563293457s
Interpretability | RDF structures check for dbnary took 0.12549281120300293s
Versatility | Serialization formats check for dbnary took 0.20264196395874023s
Availability | RDF dump link check for dbnary took 0.0764005184173584s
License | MR license check for dbnary took 0.13285160064697266s
License | HR license check for dbnary took 62.0005247592926s
Amount of data | Number of property check for dbnary took 0.11304092407226562s
Understandability | Number of label check for dbnary took 0.5475418567657471s
Understandability | URI regex check for dbnary took 0.1625354290008545s
Understandability | Vocabs check for dbnary took 0.15673232078552246s
Verifiability | Authors check for dbnary took 0.08216500282287598s
Verifiability | Publishers check for dbnary took 0.06309008598327637s
Performance | Throughput check for dbnary took 10.565457820892334s
Amount of data | Check the number of entities for dbnary took 0.00010013580322265625s
Verifiability | Contribs. check for dbnary took 0.07905173301696777s
Interlinking | sameAs chians check for dbnary took 0.09815216064453125s
Interlinking | skos check for dbnary took 0.22486662864685059s
Interlinking | skos check for dbnary took 0.07230329513549805s
Timeliness | dataset update frequency check for dbnary took 0.13217759132385254s
Currency | Creation date check for dbnary took 0.17221951484680176s
Currency | Modification date check for dbnary took 0.1839301586151123s
Rep.Conc. | URIs length for dbnary took 11.687028884887695s
Interoperability | New vocabularies check for dbnary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.09906697273254395s
Accuracy | Check Functional Property for dbnary took 0.1591050624847412s
Accuracy | Check Inverse Functional Property for dbnary took 0.12986087799072266s
Accuracy | Check Empty annotation labels for dbnary took 0.49451208114624023s
Accuracy | Check White space in annotation for dbnary took 0.03068232536315918s
Accuracy | Check Datatype consistency for dbnary took 0.028909921646118164s
Consistency | Disjoint class check for dbnary took 0.09798812866210938s
Consistency | Check Misplaced properties for dbnary took 8.98900842666626s
Consistency | Misplaced classes for dbnary took 0.2146463394165039s
Consistency | Check Ontology hijacking for dbnary took 1.7198395729064941s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.261601448059082s
Consistency | Check Invalid usage of undefined properties for dbnary took 9.95539665222168s
Conciseness | Check Extensional conciseness for dbnary took 0.031167030334472656s
Conciseness | Check Intensional conciseness for dbnary took 0.2032616138458252s
Security | Sign check for dbnary took 0.10248494148254395s
Availability | Check URIs Dereferenciability for dbnary took 9.693746089935303s
Completeness | Calculation of interlinking completeness for dbnary took 0.7451064586639404s
Reputation | Calculation of the PageRank for dbnary took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for dbnary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.1920928955078125e-06s
Believability | Calculation of trust value for dbnary took 8.106231689453125e-06s
INFO | --- Analysis for dbnary took 289.7076714038849s
Availability | SPARQL endpoint availability check for DBpedia took 0.280642032623291s
Availability | VoID file availability check for DBpedia took 0.0007047653198242188s
Extra | Recovery of all triples for DBpedia took 4.278276205062866s
Performance | Total latancy measurement for DBpedia took 0.9418282508850098s
Amount of data | Number of triples check for DBpedia took 1.4349863529205322s
Interoperability | New terms check for DBpedia took 8.58538293838501s
Versatility | Languages check for DBpedia took 30.414430618286133s
Interpretability | Number of blank nodes check for DBpedia took 0.19319963455200195s
Security | Check HTTPS for DBpedia took 0.12388181686401367s
Interpretability | RDF structures check for DBpedia took 0.7417480945587158s
Versatility | Serialization formats check for DBpedia took 0.23373150825500488s
Availability | RDF dump link check for DBpedia took 0.2228379249572754s
License | MR license check for DBpedia took 0.8493983745574951s
License | HR license check for DBpedia took 32.05303740501404s
Amount of data | Number of property check for DBpedia took 0.20227837562561035s
Understandability | Number of label check for DBpedia took 3.4790329933166504s
Understandability | URI regex check for DBpedia took 0.40468859672546387s
Understandability | Vocabs check for DBpedia took 0.3725309371948242s
Verifiability | Authors check for DBpedia took 0.28044748306274414s
Verifiability | Publishers check for DBpedia took 0.23797321319580078s
Performance | Throughput check for DBpedia took 11.465115308761597s
Amount of data | Check the number of entities for DBpedia took 7.510185241699219e-05s
Verifiability | Contribs. check for DBpedia took 0.8708782196044922s
Interlinking | sameAs chians check for DBpedia took 2.8179214000701904s
Interlinking | skos check for DBpedia took 0.8495547771453857s
Interlinking | skos check for DBpedia took 0.17656230926513672s
Timeliness | dataset update frequency check for DBpedia took 0.2170124053955078s
Currency | Creation date check for DBpedia took 0.6455435752868652s
Currency | Modification date check for DBpedia took 0.43900132179260254s
Rep.Conc. | URIs length for DBpedia took 37.30058217048645s
Interoperability | New vocabularies check for DBpedia took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.19434523582458496s
Accuracy | Check Functional Property for DBpedia took 0.34036946296691895s
Accuracy | Check Inverse Functional Property for DBpedia took 0.234405517578125s
Accuracy | Check Empty annotation labels for DBpedia took 4.3223183155059814s
Accuracy | Check White space in annotation for DBpedia took 0.030770301818847656s
Accuracy | Check Datatype consistency for DBpedia took 0.028577804565429688s
Consistency | Disjoint class check for DBpedia took 0.3965017795562744s
Consistency | Check Misplaced properties for DBpedia took 51.014851331710815s
Consistency | Misplaced classes for DBpedia took 14.313148975372314s
Consistency | Check Ontology hijacking for DBpedia took 10.138461828231812s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.223480224609375s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.6058995723724365s
Conciseness | Check Extensional conciseness for DBpedia took 0.03454017639160156s
Conciseness | Check Intensional conciseness for DBpedia took 1.1867647171020508s
Security | Sign check for DBpedia took 0.19507288932800293s
Availability | Check URIs Dereferenciability for DBpedia took 6568.129799365997s
Completeness | Calculation of interlinking completeness for DBpedia took 1.6389191150665283s
Reputation | Calculation of the PageRank for DBpedia took 0.021457433700561523s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008971691131591797s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia took 6967.80788731575s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.262434720993042s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.67572021484375e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 8.6890287399292s
Availability | SPARQL endpoint availability check for DBpedia Commons took 4.451571226119995s
Availability | VoID file availability check for DBpedia Commons took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.2517127990722656s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.818771362304688e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-commons took 15.06536078453064s
Availability | SPARQL endpoint availability check for DBpedia in German took 7.796287536621094e-05s
Availability | VoID file availability check for DBpedia in German took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.2521209716796875s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 7.295608520507812e-05s
Believability | Calculation of trust value for DBpedia in German took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-de took 3.789980173110962s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 12.142937421798706s
Availability | VoID file availability check for DBpedia in Greek took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.7089617252349854s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0001895427703857422s
Believability | Calculation of trust value for DBpedia in Greek took 1.5020370483398438e-05s
INFO | --- Analysis for dbpedia-el took 48.7813560962677s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.4693899154663086s
Availability | VoID file availability check for DBpedia in Spanish took 0.0006508827209472656s
Extra | Recovery of all triples for DBpedia in Spanish took 16.893524885177612s
Performance | Total latancy measurement for DBpedia in Spanish took 18.99792504310608s
Amount of data | Number of triples check for DBpedia in Spanish took 5.247967958450317s
Interoperability | New terms check for DBpedia in Spanish took 8.94422698020935s
Versatility | Languages check for DBpedia in Spanish took 32.07003879547119s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.4252920150756836s
Security | Check HTTPS for DBpedia in Spanish took 0.13954591751098633s
Interpretability | RDF structures check for DBpedia in Spanish took 1.2635033130645752s
Versatility | Serialization formats check for DBpedia in Spanish took 0.6380162239074707s
Availability | RDF dump link check for DBpedia in Spanish took 2.702549934387207s
License | MR license check for DBpedia in Spanish took 3.800438404083252s
License | HR license check for DBpedia in Spanish took 32.65085244178772s
Amount of data | Number of property check for DBpedia in Spanish took 0.29278087615966797s
Understandability | Number of label check for DBpedia in Spanish took 1.7277421951293945s
Understandability | URI regex check for DBpedia in Spanish took 0.7793424129486084s
Understandability | Vocabs check for DBpedia in Spanish took 0.6189863681793213s
Verifiability | Authors check for DBpedia in Spanish took 2.632352590560913s
Verifiability | Publishers check for DBpedia in Spanish took 2.1555094718933105s
Performance | Throughput check for DBpedia in Spanish took 24.72234869003296s
Amount of data | Check the number of entities for DBpedia in Spanish took 8.225440979003906e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 2.604135751724243s
Interlinking | sameAs chians check for DBpedia in Spanish took 5.263896226882935s
Interlinking | skos check for DBpedia in Spanish took 2.4476053714752197s
Interlinking | skos check for DBpedia in Spanish took 2.5398852825164795s
Timeliness | dataset update frequency check for DBpedia in Spanish took 2.3132472038269043s
Currency | Creation date check for DBpedia in Spanish took 4.8288562297821045s
Currency | Modification date check for DBpedia in Spanish took 6.499252557754517s
Rep.Conc. | URIs length for DBpedia in Spanish took 27.620615482330322s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 2.6108133792877197s
Accuracy | Check Functional Property for DBpedia in Spanish took 2.368718385696411s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 1.8096096515655518s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 11.500073432922363s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.03069472312927246s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.030546188354492188s
Consistency | Disjoint class check for DBpedia in Spanish took 4.2327001094818115s
Consistency | Check Misplaced properties for DBpedia in Spanish took 21.52254056930542s
Consistency | Misplaced classes for DBpedia in Spanish took 13.862500667572021s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 16.04871702194214s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.1524839401245117s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 19.981374263763428s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03394913673400879s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 18.179927825927734s
Security | Sign check for DBpedia in Spanish took 2.614478588104248s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 11.721102237701416s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.713869571685791s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.02248668670654297s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0009808540344238281s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00012063980102539062s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-es took 827.0617983341217s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.2176368236541748s
Availability | VoID file availability check for DBpedia in Basque took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.24257564544677734s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02152276039123535s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 2.8371810913085938e-05s
Believability | Calculation of trust value for DBpedia in Basque took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-eu took 9.090173244476318s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.18096160888671875s
Availability | VoID file availability check for DBpedia in French took 0.0007939338684082031s
Extra | Recovery of all triples for DBpedia in French took 178.2835066318512s
Performance | Total latancy measurement for DBpedia in French took 0.4036097526550293s
Amount of data | Number of triples check for DBpedia in French took 1.384887456893921s
Interoperability | New terms check for DBpedia in French took 2.2447869777679443s
Versatility | Languages check for DBpedia in French took 300.0313346385956s
Interpretability | Number of blank nodes check for DBpedia in French took 0.18550562858581543s
Security | Check HTTPS for DBpedia in French took 0.1792917251586914s
Interpretability | RDF structures check for DBpedia in French took 0.8249478340148926s
Versatility | Serialization formats check for DBpedia in French took 0.5098283290863037s
Availability | RDF dump link check for DBpedia in French took 6.587488889694214s
License | MR license check for DBpedia in French took 1.6212396621704102s
License | HR license check for DBpedia in French took 86.89677023887634s
Amount of data | Number of property check for DBpedia in French took 0.15036225318908691s
Understandability | Number of label check for DBpedia in French took 1.7935867309570312s
Understandability | URI regex check for DBpedia in French took 0.3372914791107178s
Understandability | Vocabs check for DBpedia in French took 0.18501949310302734s
Verifiability | Authors check for DBpedia in French took 0.24034810066223145s
Verifiability | Publishers check for DBpedia in French took 0.14388465881347656s
Performance | Throughput check for DBpedia in French took 10.425590515136719s
Amount of data | Check the number of entities for DBpedia in French took 2.1081340312957764s
Verifiability | Contribs. check for DBpedia in French took 0.1432952880859375s
Interlinking | sameAs chians check for DBpedia in French took 0.45041608810424805s
Interlinking | skos check for DBpedia in French took 0.29575204849243164s
Interlinking | skos check for DBpedia in French took 0.08110332489013672s
Timeliness | dataset update frequency check for DBpedia in French took 0.45595622062683105s
Currency | Creation date check for DBpedia in French took 0.27834582328796387s
Currency | Modification date check for DBpedia in French took 0.20535016059875488s
Rep.Conc. | URIs length for DBpedia in French took 60.68901991844177s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.11033749580383301s
Accuracy | Check Functional Property for DBpedia in French took 0.14371871948242188s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.11888718605041504s
Accuracy | Check Empty annotation labels for DBpedia in French took 50.206252574920654s
Accuracy | Check White space in annotation for DBpedia in French took 3.089951276779175s
Accuracy | Check Datatype consistency for DBpedia in French took 2.7535552978515625s
Consistency | Disjoint class check for DBpedia in French took 0.1908583641052246s
Consistency | Check Misplaced properties for DBpedia in French took 8.040820598602295s
Consistency | Misplaced classes for DBpedia in French took 9.996328115463257s
Consistency | Check Ontology hijacking for DBpedia in French took 56.40065956115723s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.297529935836792s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.830792188644409s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.036194324493408s
Conciseness | Check Intensional conciseness for DBpedia in French took 2.735851526260376s
Security | Sign check for DBpedia in French took 0.14228296279907227s
Availability | Check URIs Dereferenciability for DBpedia in French took 897.0290842056274s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.9824769496917725s
Reputation | Calculation of the PageRank for DBpedia in French took 0.02219223976135254s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0008552074432373047s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00013828277587890625s
Believability | Calculation of trust value for DBpedia in French took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-fr took 1828.26775598526s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9540081024169922s
Availability | VoID file availability check for DBpedia in Japanese took 4.1044206619262695s
Extra | Recovery of all triples for DBpedia in Japanese took 8.629942178726196s
Performance | Total latancy measurement for DBpedia in Japanese took 6.6380064487457275s
Amount of data | Number of triples check for DBpedia in Japanese took 31.296305656433105s
Interoperability | New terms check for DBpedia in Japanese took 18.826651334762573s
Versatility | Languages check for DBpedia in Japanese took 1.3165433406829834s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.322014570236206s
Security | Check HTTPS for DBpedia in Japanese took 0.8021574020385742s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3908648490905762s
Versatility | Serialization formats check for DBpedia in Japanese took 1.7082595825195312s
Availability | RDF dump link check for DBpedia in Japanese took 1.335700511932373s
License | MR license check for DBpedia in Japanese took 2.1858649253845215s
License | HR license check for DBpedia in Japanese took 121.33396220207214s
Amount of data | Number of property check for DBpedia in Japanese took 1.3512494564056396s
Understandability | Number of label check for DBpedia in Japanese took 7.301959753036499s
Understandability | URI regex check for DBpedia in Japanese took 2.6761693954467773s
Understandability | Vocabs check for DBpedia in Japanese took 1.3512890338897705s
Verifiability | Authors check for DBpedia in Japanese took 1.3425226211547852s
Verifiability | Publishers check for DBpedia in Japanese took 1.4004857540130615s
Performance | Throughput check for DBpedia in Japanese took 13.364956855773926s
Amount of data | Check the number of entities for DBpedia in Japanese took 7.581710815429688e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3504517078399658s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.439171552658081s
Interlinking | skos check for DBpedia in Japanese took 1.3604223728179932s
Interlinking | skos check for DBpedia in Japanese took 1.3285298347473145s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.6173405647277832s
Currency | Creation date check for DBpedia in Japanese took 2.8076257705688477s
Currency | Modification date check for DBpedia in Japanese took 2.6882853507995605s
Rep.Conc. | URIs length for DBpedia in Japanese took 140.01864671707153s
Interoperability | New vocabularies check for DBpedia in Japanese took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3322863578796387s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3573939800262451s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3682715892791748s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 4.5450544357299805s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.026332616806030273s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.028002023696899414s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4911985397338867s
Consistency | Check Misplaced properties for DBpedia in Japanese took 122.63887786865234s
Consistency | Misplaced classes for DBpedia in Japanese took 3.7490429878234863s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.880446672439575s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.2564723491668701s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.59849810600281s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03275942802429199s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 5.135441541671753s
Security | Sign check for DBpedia in Japanese took 1.365175724029541s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 9.64985203742981s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.6308608055114746s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.023488759994506836s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010800361633300781s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia-ja took 1229.11825633049s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.4345855712890625e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.28463006019592285s
Reputation | Calculation of the PageRank for dbpedia lite took 0.02125263214111328s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00011301040649414062s
Believability | Calculation of trust value for dbpedia lite took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-lite took 24.183135747909546s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.2438507080078125e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.6990852355957031s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020804166793823242s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.147125244140625e-05s
Believability | Calculation of trust value for DBpedia-Live took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-live took 3.8476696014404297s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.2834339141845703s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.28238821029663086s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020826101303100586s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016832351684570312s
Believability | Calculation of trust value for DBpedia in Dutch took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-nl took 3.809201955795288s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 30.13533115386963s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.28609323501586914s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.225440979003906e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia-pt took 73.12711024284363s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.315376281738281e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.25595593452453613s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.021526336669921875s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0008885860443115234s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.6716461181640625e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-spotlight took 4.183804750442505s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.363059997558594e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.27054762840270996s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.021052837371826172s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 7.343292236328125e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 14.289514303207397s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 5.6743621826171875e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.2792699337005615s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.2901763916015625e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-wikidata took 2.962902307510376s
Availability | SPARQL endpoint availability check for DBpedia took 4.267692565917969e-05s
Availability | VoID file availability check for DBpedia took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for DBpedia took 0.28210997581481934s
Reputation | Calculation of the PageRank for DBpedia took 0.021166324615478516s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.24249267578125e-05s
Believability | Calculation of trust value for DBpedia took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia_ took 2.9260640144348145s
Availability | SPARQL endpoint availability check for DBTropes took 4.363059997558594e-05s
Availability | VoID file availability check for DBTropes took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for DBTropes took 0.2791001796722412s
Reputation | Calculation of the PageRank for DBTropes took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.5367431640625e-05s
Believability | Calculation of trust value for DBTropes took 7.3909759521484375e-06s
INFO | --- Analysis for dbtropes took 3.0281193256378174s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 5.555152893066406e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.28376245498657227s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.886222839355469e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 6.67572021484375e-06s
INFO | --- Analysis for dbtune took 2.958479881286621s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.315376281738281e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2578299045562744s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.021115541458129883s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.001016378402709961s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 6.604194641113281e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 8.344650268554688e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.555957555770874s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.3392181396484375e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.26276516914367676s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020866870880126953s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.457069396972656e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.924502372741699s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.875833988189697s
Availability | VoID file availability check for DBTune.org/classical took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.25406455993652344s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020833253860473633s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.677078247070312e-05s
Believability | Calculation of trust value for DBTune.org/classical took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-classical took 22.40364408493042s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.337918519973755s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.28056907653808594s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.890296936035156e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 28.226773500442505s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.325862407684326s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2725026607513428s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 9.918212890625e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 8.106231689453125e-06s
INFO | --- Analysis for dbtune-magnatune took 24.441463470458984s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.338073253631592s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.2868976593017578s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020276546478271484s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010776519775390625s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.92215657234192s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.327426671981812s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.25911903381347656s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020452499389648438s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.0067901611328125e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 8.106231689453125e-06s
INFO | --- Analysis for dbtune-myspace took 17.872878551483154s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.315376281738281e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.2821478843688965s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020381927490234375s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 7.867813110351562e-06s
INFO | --- Analysis for dclg-openuplabs took 2.8769333362579346s
Availability | SPARQL endpoint availability check for data.dcs took 8.344650268554688e-05s
Availability | VoID file availability check for data.dcs took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for data.dcs took 0.2626485824584961s
Reputation | Calculation of the PageRank for data.dcs took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.961822509765625e-05s
Believability | Calculation of trust value for data.dcs took 6.4373016357421875e-06s
INFO | --- Analysis for dcs-sheffield took 2.5258679389953613s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.267692565917969e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.6836221218109131s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020557880401611328s
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.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 2.9325485229492188e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 7.3909759521484375e-06s
INFO | --- Analysis for de-budget took 3.2937238216400146s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.458427429199219e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2617006301879883s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.790855407714844e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 8.821487426757812e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.3162477016448975s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.458427429199219e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0008037090301513672s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.2713310718536377s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.3392181396484375e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 6.67572021484375e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.364015817642212s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 5.4836273193359375e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.2552926540374756s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020540714263916016s
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.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 2.86102294921875e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.9013876914978027s
Availability | SPARQL endpoint availability check for Demografie took 4.1961669921875e-05s
Availability | VoID file availability check for Demografie took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Demografie took 0.27823543548583984s
Reputation | Calculation of the PageRank for Demografie took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Demografie took 2.8371810913085938e-05s
Believability | Calculation of trust value for Demografie took 7.3909759521484375e-06s
INFO | --- Analysis for demografie took 2.889265775680542s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.2438507080078125e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.27065014839172363s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.218650817871094e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 6.9141387939453125e-06s
INFO | --- Analysis for desaparecidos took 2.7844741344451904s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.2438507080078125e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2612035274505615s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.632110595703125e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 7.3909759521484375e-06s
INFO | --- Analysis for deustoentrepreneurship took 4.210308790206909s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.3392181396484375e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.2733645439147949s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010704994201660156s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 7.152557373046875e-06s
INFO | --- Analysis for deustotech took 4.371715545654297s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3872745037078857s
Availability | VoID file availability check for Deutsche Biographie took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.2604091167449951s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020488977432250977s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.790855407714844e-05s
Believability | Calculation of trust value for Deutsche Biographie took 6.4373016357421875e-06s
INFO | --- Analysis for deutsche-biographie took 4.087076902389526s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.673004150390625e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0003285408020019531s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2751743793487549s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020435810089111328s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.2928924560546875e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 7.3909759521484375e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.7670698165893555s
Availability | SPARQL endpoint availability check for dev8d took 4.458427429199219e-05s
Availability | VoID file availability check for dev8d took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for dev8d took 0.2603285312652588s
Reputation | Calculation of the PageRank for dev8d took 0.020610570907592773s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.43865966796875e-05s
Believability | Calculation of trust value for dev8d took 7.3909759521484375e-06s
INFO | --- Analysis for dev8d took 2.760359764099121s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.124459743499756s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.25789809226989746s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.0207977294921875s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.364418029785156e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 7.3909759521484375e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.67110013961792s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.38690185546875e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.2836334705352783s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.0994415283203125e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 8.106231689453125e-06s
INFO | --- Analysis for DHSVM took 18.664987325668335s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.363059997558594e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.3227102756500244s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.170967102050781e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 8.344650268554688e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.906693935394287s
Availability | SPARQL endpoint availability check for Diavgeia took 4.410743713378906e-05s
Availability | VoID file availability check for Diavgeia took 0.0008051395416259766s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.28014230728149414s
Reputation | Calculation of the PageRank for Diavgeia took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.678436279296875e-05s
Believability | Calculation of trust value for Diavgeia took 1.0251998901367188e-05s
INFO | --- Analysis for diavgeia took 5.645176887512207s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 5.53131103515625e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.24903583526611328s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011920928955078125s
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 8.12733268737793s
Availability | SPARQL endpoint availability check for diigo.feed took 4.172325134277344e-05s
Availability | VoID file availability check for diigo.feed took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.2549734115600586s
Reputation | Calculation of the PageRank for diigo.feed took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 3.1948089599609375e-05s
Believability | Calculation of trust value for diigo.feed took 7.3909759521484375e-06s
INFO | --- Analysis for diigo-feed took 2.8573262691497803s
Availability | SPARQL endpoint availability check for DisGeNET took 0.9611215591430664s
Availability | VoID file availability check for DisGeNET took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.2677145004272461s
Reputation | Calculation of the PageRank for DisGeNET took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015211105346679688s
Believability | Calculation of trust value for DisGeNET took 9.298324584960938e-06s
INFO | --- Analysis for disgenet took 8.720431566238403s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.267692565917969e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.2604343891143799s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.02090597152709961s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 7.867813110351562e-06s
INFO | --- Analysis for disk took 2.907640218734741s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.220008850097656e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.2758932113647461s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.024979591369628906s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.0279159545898438e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 1.1920928955078125e-05s
INFO | --- Analysis for distritos-zaragoza took 2.9456534385681152s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.482269287109375e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0013933181762695312s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2511892318725586s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.0279159545898438e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 8.106231689453125e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 9.312071561813354s
Availability | SPARQL endpoint availability check for DM2E took 5.1021575927734375e-05s
Availability | VoID file availability check for DM2E took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for DM2E took 0.38547515869140625s
Reputation | Calculation of the PageRank for DM2E took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DM2E took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.0001068115234375s
Believability | Calculation of trust value for DM2E took 6.9141387939453125e-06s
INFO | --- Analysis for dm2e took 3.270594358444214s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.029273986816406e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.2760927677154541s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 2.8371810913085938e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.867813110351562e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.9527828693389893s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.8631350994110107s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.3013327121734619s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020632266998291016s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00020432472229003906s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 7.152557373046875e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 11.24885106086731s
Availability | SPARQL endpoint availability check for DOAP Store took 4.220008850097656e-05s
Availability | VoID file availability check for DOAP Store took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.255382776260376s
Reputation | Calculation of the PageRank for DOAP Store took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.123283386230469e-05s
Believability | Calculation of trust value for DOAP Store took 6.9141387939453125e-06s
INFO | --- Analysis for doap_store took 2.806018590927124s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.38690185546875e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.24811530113220215s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020986080169677734s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.341934204101562e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.9604644775390625e-06s
INFO | --- Analysis for doi took 8.053685426712036s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.267692565917969e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.24810791015625s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.123283386230469e-05s
Believability | Calculation of trust value for Driggu Florentino took 9.5367431640625e-06s
INFO | --- Analysis for Driggu took 3.200714349746704s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.089423656463623s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.26895999908447266s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.647804260253906e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 6.67572021484375e-06s
INFO | --- Analysis for drug-data-hifm took 36.58326768875122s
Availability | SPARQL endpoint availability check for dspace took 4.220008850097656e-05s
Availability | VoID file availability check for dspace took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for dspace took 0.2547190189361572s
Reputation | Calculation of the PageRank for dspace took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for dspace took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for dspace took 3.123283386230469e-05s
Believability | Calculation of trust value for dspace took 6.9141387939453125e-06s
INFO | --- Analysis for dspace took 2.9805970191955566s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.267692565917969e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2842261791229248s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.0994415283203125e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 7.3909759521484375e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.944416046142578s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.22285318374634s
Availability | VoID file availability check for MetaLex Document Server took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.26886439323425293s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.021097660064697266s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0008339881896972656s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.910064697265625e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.152557373046875e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 554.5425450801849s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.215719699859619s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.2565028667449951s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007197856903076172s
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.867813110351562e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 13.92838191986084s
Availability | SPARQL endpoint availability check for DWS-Group took 6.866455078125e-05s
Availability | VoID file availability check for DWS-Group took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.2783777713775635s
Reputation | Calculation of the PageRank for DWS-Group took 0.02050948143005371s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010323524475097656s
Believability | Calculation of trust value for DWS-Group took 7.3909759521484375e-06s
INFO | --- Analysis for dws-group took 3.9448134899139404s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.38690185546875e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.2696352005004883s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.8133392333984375e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 7.62939453125e-06s
INFO | --- Analysis for E1 took 5.009297847747803s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.06506872177124023s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2594301700592041s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.0001125335693359375s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-alaska took 3.498378038406372s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.04243183135986328s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.26880502700805664s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.030632019042969e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-cau took 3.4551446437835693s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.03457045555114746s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2755005359649658s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.67572021484375e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.883841037750244s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.03647041320800781s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.27436375617980957s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 0.00010085105895996094s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.4452812671661377s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.03275465965270996s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.25537657737731934s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013136863708496094s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.4403815269470215s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.044660091400146484s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.27818870544433594s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 9.894371032714844e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-famu took 2.482604742050171s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04275989532470703s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.2780954837799072s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020829439163208008s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012969970703125s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-harvard took 2.4461567401885986s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.04769492149353027s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2642219066619873s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.021163225173950195s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00013589859008789062s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.4841363430023193s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.03894209861755371s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.28234171867370605s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.556510925292969e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 8.821487426757812e-06s
INFO | --- Analysis for eagle-i-howard took 2.452730417251587s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.056206464767456055s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2849571704864502s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0008900165557861328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.963180541992188e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.51603102684021s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04033517837524414s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.2524127960205078s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.02086615562438965s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0008685588836669922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011968612670898438s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-jsu took 2.4884510040283203s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.07154679298400879s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.26168298721313477s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.506111145019531e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-meharry took 2.542372941970825s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.08083224296569824s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0012056827545166016s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2822995185852051s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.799003601074219e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 9.775161743164062e-06s
INFO | --- Analysis for eagle-i-montana took 2.5250370502471924s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.045041561126708984s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.25752830505371094s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.02091503143310547s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.560585021972656e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-msm took 2.48594069480896s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.04327702522277832s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2715880870819092s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.021117448806762695s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00013113021850585938s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.4262917041778564s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.03124380111694336s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2682335376739502s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.532669067382812e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-psm took 2.4136831760406494s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.03554272651672363s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.2387096881866455s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-tsu took 2.435197114944458s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.04459667205810547s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2438647747039795s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 7.367134094238281e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.371403455734253s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.03662419319152832s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0003757476806640625s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.2679100036621094s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.5367431640625e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.4076080322265625s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.033800601959228516s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.23415803909301758s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012421607971191406s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-upr took 2.3099308013916016s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.0374906063079834s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.2699880599975586s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.079673767089844e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-utep took 2.342433452606201s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.037734031677246094s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2560603618621826s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020894765853881836s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.224082946777344e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.6689300537109375e-05s
INFO | --- Analysis for eagle-i-utsa took 2.386718273162842s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.15925860404968262s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.2575242519378662s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.202957153320312e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.4731462001800537s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.04288506507873535s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.253021240234375s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.02046036720275879s
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.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.295608520507812e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-xula took 2.3929152488708496s
Availability | SPARQL endpoint availability check for Emergency situation took 1.6153473854064941s
Availability | VoID file availability check for Emergency situation took 0.000354766845703125s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.2695314884185791s
Reputation | Calculation of the PageRank for Emergency situation took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 8.630752563476562e-05s
Believability | Calculation of trust value for Emergency situation took 6.67572021484375e-06s
INFO | --- Analysis for Earthquake took 4.498106956481934s
Availability | SPARQL endpoint availability check for ESO took 0.658597469329834s
Availability | VoID file availability check for ESO took 0.00036406517028808594s
Completeness | Calculation of interlinking completeness for ESO took 0.2672903537750244s
Reputation | Calculation of the PageRank for ESO took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for ESO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for ESO took 7.987022399902344e-05s
Believability | Calculation of trust value for ESO took 7.152557373046875e-06s
INFO | --- Analysis for Earthquake_case took 4.268537521362305s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.3976404666900635s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.26779603958129883s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010061264038085938s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for ecb-linked-data took 2.7855424880981445s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.069068193435669s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.000392913818359375s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.23897957801818848s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.3855438232421875e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.245208740234375e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 9.930178880691528s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.9748919010162354s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2578411102294922s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.021144628524780273s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 7.200241088867188e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.11051344871521s
Availability | SPARQL endpoint availability check for ECLAP took 20.632023096084595s
Availability | VoID file availability check for ECLAP took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for ECLAP took 0.2923903465270996s
Reputation | Calculation of the PageRank for ECLAP took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.410743713378906e-05s
Believability | Calculation of trust value for ECLAP took 7.62939453125e-06s
INFO | --- Analysis for eclap took 53.11260747909546s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.4345855712890625e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2596724033355713s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.0728836059570312e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 7.62939453125e-06s
INFO | --- Analysis for ECNU-GISer took 4.156733989715576s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.4345855712890625e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.25865697860717773s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02027606964111328s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.1975250244140625e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.62939453125e-06s
INFO | --- Analysis for ecs took 2.7163891792297363s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.5299530029296875e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.2720928192138672s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.021033763885498047s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.075599670410156e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 6.9141387939453125e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.9563281536102295s
Availability | SPARQL endpoint availability check for Edublogs took 4.4345855712890625e-05s
Availability | VoID file availability check for Edublogs took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Edublogs took 0.28852295875549316s
Reputation | Calculation of the PageRank for Edublogs took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.799003601074219e-05s
Believability | Calculation of trust value for Edublogs took 8.106231689453125e-06s
INFO | --- Analysis for edublogs took 3.3814821243286133s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5390434265136719s
Availability | VoID file availability check for education.data.gov.uk took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.24627065658569336s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.322166442871094e-05s
Believability | Calculation of trust value for education.data.gov.uk took 6.4373016357421875e-06s
INFO | --- Analysis for education-data-gov-uk took 5.173871040344238s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 6.866455078125e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2654104232788086s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 1.8358230590820312e-05s
INFO | --- Analysis for education-openuplabs took 2.936509847640991s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 393.36025071144104s
Availability | VoID file availability check for Educational programs - SISVU took 0.0012717247009277344s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 1.394385576248169s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02147984504699707s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.507469177246094e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.33514404296875e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1323.7010221481323s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.6086931228637695s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.7044854164123535s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.814697265625e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 4.5299530029296875e-06s
INFO | --- Analysis for eea took 18.48619556427002s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5580265522003174s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.2647104263305664s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.14984130859375e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.245208740234375e-06s
INFO | --- Analysis for eea-rod took 6.714663743972778s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.17431855201721191s
Availability | VoID file availability check for EEA Vocabularies took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.27292561531066895s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.021924495697021484s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 9.298324584960938e-05s
Believability | Calculation of trust value for EEA Vocabularies took 8.344650268554688e-06s
INFO | --- Analysis for eea-vocabularies took 5.825636625289917s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 4.076957702636719e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.24854779243469238s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0009963512420654297s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.457069396972656e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for ege-university-linked-open-data took 3.374056577682495s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.4329972267150879s
Availability | VoID file availability check for E-Government Ontology took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2765936851501465s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 2.7179718017578125e-05s
Believability | Calculation of trust value for E-Government Ontology took 9.775161743164062e-06s
INFO | --- Analysis for EGovOntology took 3.363680124282837s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7019205093383789s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007562637329101562s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.6729629039764404s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2431347370147705s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.04746413230896s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.839411973953247s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.442710399627686s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 5.494624137878418s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.648979663848877s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9017770290374756s
