Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.506111145019531e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.253063440322876s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.4908909797668457s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.000335693359375s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.1444091796875e-05s
INFO | --- Analysis for 0080-3626 took 6.54827618598938s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.363059997558594e-05s
Availability | VoID file availability check for 土地利用图 took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.27897167205810547s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020268678665161133s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 4.076957702636719e-05s
Believability | Calculation of trust value for 土地利用图 took 1.1444091796875e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 3.2687058448791504s
Availability | SPARQL endpoint availability check for 113322 took 4.1961669921875e-05s
Availability | VoID file availability check for 113322 took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for 113322 took 0.2603776454925537s
Reputation | Calculation of the PageRank for 113322 took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for 113322 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.9087066650390625e-05s
Believability | Calculation of trust value for 113322 took 6.67572021484375e-06s
INFO | --- Analysis for 11 took 4.753535509109497s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 6.771087646484375e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.27237749099731445s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020151615142822266s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 2.7179718017578125e-05s
Believability | Calculation of trust value for Korepetycje Buki took 7.152557373046875e-06s
INFO | --- Analysis for 12323 took 2.8095500469207764s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0795128345489502s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2668039798736572s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007033348083496094s
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 6.9141387939453125e-06s
INFO | --- Analysis for 2000-us-census-rdf took 2.8929030895233154s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.8214826583862305s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2611813545227051s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020071983337402344s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 4.0531158447265625e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.019075870513916s
Availability | SPARQL endpoint availability check for Open Data Web took 0.12497544288635254s
Availability | VoID file availability check for Open Data Web took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.25443553924560547s
Reputation | Calculation of the PageRank for Open Data Web took 0.026980876922607422s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0013720989227294922s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 4.4345855712890625e-05s
Believability | Calculation of trust value for Open Data Web took 7.3909759521484375e-06s
INFO | --- Analysis for _data.odw.tw took 2.994889497756958s
Availability | SPARQL endpoint availability check for 土地利用 took 4.506111145019531e-05s
Availability | VoID file availability check for 土地利用 took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2930786609649658s
Reputation | Calculation of the PageRank for 土地利用 took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.62396240234375e-05s
Believability | Calculation of trust value for 土地利用 took 6.67572021484375e-06s
INFO | --- Analysis for _data1.odw.tw took 2.424938440322876s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.3392181396484375e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2574808597564697s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.7179718017578125e-05s
Believability | Calculation of trust value for 土地利用模型 took 6.4373016357421875e-06s
INFO | --- Analysis for _data2.odw.tw took 5.701604127883911s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.2438507080078125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.28495073318481445s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020272254943847656s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8133392333984375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.773193597793579s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.291534423828125e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0010650157928466797s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.26111936569213867s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.765655517578125e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 7.867813110351562e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 2.969968318939209s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.172325134277344e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.25440549850463867s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.00077056884765625s
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.801598310470581s
Availability | SPARQL endpoint availability check for SummerOlympics took 21.529916524887085s
Availability | VoID file availability check for SummerOlympics took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.2537801265716553s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02038407325744629s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.67572021484375e-05s
Believability | Calculation of trust value for SummerOlympics took 7.152557373046875e-06s
INFO | --- Analysis for abc took 49.84533929824829s
Availability | SPARQL endpoint availability check for Test_m took 4.124641418457031e-05s
Availability | VoID file availability check for Test_m took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Test_m took 0.27503371238708496s
Reputation | Calculation of the PageRank for Test_m took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for Test_m took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Test_m took 2.765655517578125e-05s
Believability | Calculation of trust value for Test_m took 7.3909759521484375e-06s
INFO | --- Analysis for ABC took 2.3989267349243164s
Availability | SPARQL endpoint availability check for my intro took 4.172325134277344e-05s
Availability | VoID file availability check for my intro took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for my intro took 0.26450204849243164s
Reputation | Calculation of the PageRank for my intro took 0.02025890350341797s
Interlinking | Calculation of Degree of Connection for my intro took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for my intro took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for my intro took 2.6464462280273438e-05s
Believability | Calculation of trust value for my intro took 7.152557373046875e-06s
INFO | --- Analysis for abhay_intro took 2.401831865310669s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.8833038806915283s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00035834312438964844s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.2676248550415039s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020100116729736328s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010395050048828125s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for abs-linked-data took 3.2274065017700195s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 5.936622619628906e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.250751256942749s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.9087066650390625e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 7.62939453125e-06s
INFO | --- Analysis for academic-offer-of-unl took 3.3792152404785156s
Availability | SPARQL endpoint availability check for AcadOnto took 4.1961669921875e-05s
Availability | VoID file availability check for AcadOnto took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.26992034912109375s
Reputation | Calculation of the PageRank for AcadOnto took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for AcadOnto took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.765655517578125e-05s
Believability | Calculation of trust value for AcadOnto took 6.9141387939453125e-06s
INFO | --- Analysis for acadonto took 2.878171443939209s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.025377035140991s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2787327766418457s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020133018493652344s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.57763671875e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.76837158203125e-06s
INFO | --- Analysis for acorn-sat took 51.249186754226685s
Availability | SPARQL endpoint availability check for Addgene took 4.1961669921875e-05s
Availability | VoID file availability check for Addgene took 0.0008227825164794922s
Completeness | Calculation of interlinking completeness for Addgene took 0.2650275230407715s
Reputation | Calculation of the PageRank for Addgene took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for Addgene took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.3855438232421875e-05s
Believability | Calculation of trust value for Addgene took 7.152557373046875e-06s
INFO | --- Analysis for addgene took 15.802758932113647s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.1961669921875e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0008966922760009766s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.23824548721313477s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020097970962524414s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.822845458984375e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 7.3909759521484375e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 7.967532396316528s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.5234518051147461s
Availability | VoID file availability check for AEMET metereological dataset took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.28493309020996094s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020084142684936523s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.4332275390625e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 6.198883056640625e-06s
INFO | --- Analysis for aemet took 4.766505718231201s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.100799560546875e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.2873353958129883s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 2.6941299438476562e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 6.9141387939453125e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.9038195610046387s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.0323796272277832s
Availability | VoID file availability check for AgriNepalData took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2630488872528076s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.033348083496094e-05s
Believability | Calculation of trust value for AgriNepalData took 1.3113021850585938e-05s
INFO | --- Analysis for agrinepaldata took 2.4408276081085205s
Availability | SPARQL endpoint availability check for AGRIS took 262.2763776779175s
Availability | VoID file availability check for AGRIS took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for AGRIS took 0.25392985343933105s
Reputation | Calculation of the PageRank for AGRIS took 0.021302461624145508s
Interlinking | Calculation of Degree of Connection for AGRIS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for AGRIS took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.82012939453125e-05s
Believability | Calculation of trust value for AGRIS took 7.3909759521484375e-06s
INFO | --- Analysis for agris took 557.4456238746643s
Availability | SPARQL endpoint availability check for AGROVOC took 0.20095157623291016s
Availability | VoID file availability check for AGROVOC took 0.0006449222564697266s
Extra | Recovery of all triples for AGROVOC took 31.735748052597046s
Performance | Total latancy measurement for AGROVOC took 0.4421839714050293s
Amount of data | Number of triples check for AGROVOC took 30.09566903114319s
Interoperability | New terms check for AGROVOC took 3.353884220123291s
Versatility | Languages check for AGROVOC took 30.084155559539795s
Interpretability | Number of blank nodes check for AGROVOC took 30.0859637260437s
Interpretability | RDF structures check for AGROVOC took 0.08602571487426758s
Versatility | Serialization formats check for AGROVOC took 0.09151959419250488s
Availability | RDF dump link check for AGROVOC took 0.0912625789642334s
License | MR license check for AGROVOC took 0.09324812889099121s
License | HR license check for AGROVOC took 0.583486795425415s
Amount of data | Number of property check for AGROVOC took 0.09867668151855469s
Understandability | Number of label check for AGROVOC took 30.099153518676758s
Understandability | URI regex check for AGROVOC took 0.16959595680236816s
Understandability | Vocabs check for AGROVOC took 0.0792534351348877s
Verifiability | Authors check for AGROVOC took 0.10151410102844238s
Verifiability | Publishers check for AGROVOC took 0.07699704170227051s
Performance | Throughput check for AGROVOC took 10.532147407531738s
Amount of data | Check the number of entities for AGROVOC took 7.534027099609375e-05s
Verifiability | Contribs. check for AGROVOC took 0.07999587059020996s
Interlinking | sameAs chians check for AGROVOC took 0.09270381927490234s
Interlinking | skos check for AGROVOC took 11.580153226852417s
Interlinking | skos check for AGROVOC took 15.922678709030151s
Timeliness | dataset update frequency check for AGROVOC took 0.08398246765136719s
Currency | Creation date check for AGROVOC took 0.19061684608459473s
Currency | Modification date check for AGROVOC took 0.17890048027038574s
Rep.Conc. | URIs length for AGROVOC took 47.94150495529175s
Interoperability | New vocabularies check for AGROVOC took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.10013341903686523s
Accuracy | Check Empty annotation labels for AGROVOC took 17.95966100692749s
Accuracy | Check White space in annotation for AGROVOC took 2.9783825874328613s
Consistency | Disjoint class check for AGROVOC took 0.08395671844482422s
Consistency | Check Misplaced properties for AGROVOC took 16.181612968444824s
Consistency | Check Ontology hijacking for AGROVOC took 30.082755088806152s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 17.11650848388672s
Conciseness | Check Extensional conciseness for AGROVOC took 0.000164031982421875s
Conciseness | Check Intensional conciseness for AGROVOC took 0.09066033363342285s
Security | Sign check for AGROVOC took 0.09129476547241211s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.4345982074737549s
Reputation | Calculation of the PageRank for AGROVOC took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011539459228515625s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.6689300537109375e-06s
Believability | Calculation of trust value for AGROVOC took 7.152557373046875e-06s
INFO | --- Analysis for agrovoc took 405.99784803390503s
Availability | SPARQL endpoint availability check for AGROVOC took 4.124641418457031e-05s
Availability | VoID file availability check for AGROVOC took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.25493431091308594s
Reputation | Calculation of the PageRank for AGROVOC took 0.02024674415588379s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0008347034454345703s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 6.413459777832031e-05s
Believability | Calculation of trust value for AGROVOC took 8.344650268554688e-06s
INFO | --- Analysis for agrovoc-skos took 4.178844690322876s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.274641990661621s
Availability | VoID file availability check for Analytics India Magazine took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.2592487335205078s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.075599670410156e-05s
Believability | Calculation of trust value for Analytics India Magazine took 7.3909759521484375e-06s
INFO | --- Analysis for AIM took 6.0264317989349365s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.220008850097656e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.2598302364349365s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 2.8848648071289062e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 6.4373016357421875e-06s
INFO | --- Analysis for AISHE took 2.2818520069122314s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for  equipment ontology took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.2687413692474365s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020170927047729492s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 2.7179718017578125e-05s
Believability | Calculation of trust value for  equipment ontology took 6.67572021484375e-06s
INFO | --- Analysis for akash took 3.183749198913574s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.029273986816406e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.27144932746887207s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007092952728271484s
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.152557373046875e-06s
INFO | --- Analysis for aksworg took 3.8246729373931885s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.1484832763671875e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.2684957981109619s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.075599670410156e-05s
Believability | Calculation of trust value for AlchemyAPI took 7.62939453125e-06s
INFO | --- Analysis for alchemyapi took 2.95393705368042s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.076957702636719e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.2618739604949951s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.956390380859375e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 7.62939453125e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.8734493255615234s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.1553764343261719s
Availability | VoID file availability check for aliada-scanbit-net took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.2402181625366211s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00010704994201660156s
Believability | Calculation of trust value for aliada-scanbit-net took 7.152557373046875e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.386423826217651s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.029273986816406e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.000244140625s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.2380833625793457s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.7894973754882812e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 7.62939453125e-06s
INFO | --- Analysis for allen-brain-atlas took 2.8650362491607666s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.6808996200561523s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006628036499023438s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 137.59822869300842s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7097742557525635s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.5297183990478516s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.6069250106811523s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.1035010814667s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.465672492980957s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.9533905982971191s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.7712950706481934s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.7676362991333008s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.722639799118042s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.6260690689086914s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 32.81940221786499s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5686986446380615s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.749518632888794s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.0971927642822266s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.6334564685821533s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6235232353210449s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.6387538909912109s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.957972049713135s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 8.20159912109375e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5383617877960205s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5575046539306641s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6342267990112305s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6182763576507568s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.6901986598968506s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.2674100399017334s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1857542991638184s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 53.59350657463074s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 4.712686777114868s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5532224178314209s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.5826945304870605s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.5664618015289307s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 34.46139192581177s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.050072193145752s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.6621100902557373s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.5936827659606934s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.975247144699097s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.83274507522583s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 31.728187561035156s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.407085657119751s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.847430229187012s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7497546672821045s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8354682922363281s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.546699047088623s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12459.51289844513s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.6558589935302734s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02300262451171875s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0008864402770996094s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.0108642578125e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 2.920278310775757s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 7.152557373046875e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13212.127886295319s
Availability | SPARQL endpoint availability check for Alojamientos took 4.410743713378906e-05s
Availability | VoID file availability check for Alojamientos took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.28025007247924805s
Reputation | Calculation of the PageRank for Alojamientos took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for Alojamientos took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.0517578125e-05s
Believability | Calculation of trust value for Alojamientos took 1.4781951904296875e-05s
INFO | --- Analysis for alojamientos-zaragoza took 3.85068678855896s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.29968833923339844s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.24828624725341797s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.022099733352661133s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0010254383087158203s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.2438507080078125e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.3113021850585938e-05s
INFO | --- Analysis for alpino-rdf took 4.328449010848999s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.3392181396484375e-05s
Availability | VoID file availability check for AAT-atawil took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2544896602630615s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020964384078979492s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.6716461181640625e-05s
Believability | Calculation of trust value for AAT-atawil took 6.67572021484375e-06s
INFO | --- Analysis for Altawil took 2.3662712574005127s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 6.651878356933594e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.2697873115539551s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.02014613151550293s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 2.86102294921875e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 8.106231689453125e-06s
INFO | --- Analysis for am-collections-online took 2.8893332481384277s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.3392181396484375e-05s
Availability | VoID file availability check for Amer Nejma took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.26653099060058594s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 2.7179718017578125e-05s
Believability | Calculation of trust value for Amer Nejma took 7.152557373046875e-06s
INFO | --- Analysis for Amer_Nejma took 2.3033246994018555s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.2889983654022217s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 8.58306884765625e-06s
INFO | --- Analysis for amon took 2.951896905899048s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.6930050849914551s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.26815223693847656s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.441375732421875e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 7.152557373046875e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.8149359226226807s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.100799560546875e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.27970027923583984s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020505189895629883s
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.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.075599670410156e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 7.3909759521484375e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.895470380783081s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 6.747245788574219e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.252072811126709s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.790855407714844e-05s
Believability | Calculation of trust value for Animal Diversity Web took 7.3909759521484375e-06s
INFO | --- Analysis for animal-diversity-web took 2.820988893508911s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.482269287109375e-05s
Availability | VoID file availability check for Anime Dataset took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.25524044036865234s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.123283386230469e-05s
Believability | Calculation of trust value for Anime Dataset took 8.106231689453125e-06s
INFO | --- Analysis for Anime took 3.555842399597168s
Availability | SPARQL endpoint availability check for ANNO took 4.363059997558594e-05s
Availability | VoID file availability check for ANNO took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for ANNO took 0.26903557777404785s
Reputation | Calculation of the PageRank for ANNO took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.719329833984375e-05s
Believability | Calculation of trust value for ANNO took 6.9141387939453125e-06s
INFO | --- Analysis for anno took 4.314704656600952s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.363059997558594e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.25173068046569824s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.891654968261719e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 7.152557373046875e-06s
INFO | --- Analysis for AntiqueCarsCollection took 4.511182546615601s
Availability | SPARQL endpoint availability check for apache took 4.1961669921875e-05s
Availability | VoID file availability check for apache took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for apache took 0.273820161819458s
Reputation | Calculation of the PageRank for apache took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for apache took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for apache took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for apache took 5.9604644775390625e-05s
Believability | Calculation of trust value for apache took 7.3909759521484375e-06s
INFO | --- Analysis for apache took 3.2542853355407715s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.744529724121094e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2622959613800049s
Reputation | Calculation of the PageRank for Apertium RDF took 0.029368877410888672s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.887580871582031e-05s
Believability | Calculation of trust value for Apertium RDF took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf took 5.019618034362793s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.839897155761719e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.27732062339782715s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020998477935791016s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.9591064453125e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 2.3126602172851562e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 5.709997653961182s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.28160929679870605s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 5.0067901611328125e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.624621152877808s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.2772059440612793s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020930051803588867s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.76837158203125e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.592181444168091s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.259674072265625s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.558267593383789s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2553434371948242s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02040863037109375s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 5.0067901611328125e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.5971527099609375s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.00034308433532714844s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.2520277500152588s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.50286078453064s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 5.1021575927734375e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2593882083892822s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.516387462615967s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2815868854522705s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 5.4836273193359375e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.648736000061035s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.57763671875e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2715945243835449s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020432710647583008s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.5533201694488525s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2677731513977051s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.641387701034546s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0007982254028320312s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.2547132968902588s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 24.95597553253174s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.26485133171081543s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 5.74888014793396s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.28458452224731445s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.5560619831085205s
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.0006353855133056641s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.25766825675964355s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02095937728881836s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.547121047973633s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.25208091735839844s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.5136191844940186s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.27180051803588867s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.583845615386963s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.2574784755706787s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.646980047225952s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2785639762878418s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.4968883991241455s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 8.678436279296875e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.26230311393737793s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0008614063262939453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.497455835342407s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2874631881713867s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.5263988971710205s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.6253204345703125e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2689476013183594s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02028965950012207s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007367134094238281s
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 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.609488010406494s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 6.270408630371094e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.29700422286987305s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.283463954925537s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.7993216514587402s
Availability | VoID file availability check for AragoDBPedia took 0.0006434917449951172s
Extra | Recovery of all triples for AragoDBPedia took 3.6270289421081543s
Performance | Total latancy measurement for AragoDBPedia took 1.9417157173156738s
Amount of data | Number of triples check for AragoDBPedia took 0.8604123592376709s
Interoperability | New terms check for AragoDBPedia took 2.195374011993408s
Versatility | Languages check for AragoDBPedia took 60.46910500526428s
Interpretability | Number of blank nodes check for AragoDBPedia took 5.040734767913818s
Security | Check HTTPS for AragoDBPedia took 0.2777121067047119s
Interpretability | RDF structures check for AragoDBPedia took 0.6230497360229492s
Versatility | Serialization formats check for AragoDBPedia took 1.1310014724731445s
Availability | RDF dump link check for AragoDBPedia took 0.44028472900390625s
License | MR license check for AragoDBPedia took 0.7451159954071045s
License | HR license check for AragoDBPedia took 7.795063018798828s
Amount of data | Number of property check for AragoDBPedia took 0.39221787452697754s
Understandability | Number of label check for AragoDBPedia took 0.5987131595611572s
Understandability | URI regex check for AragoDBPedia took 0.9776082038879395s
Understandability | Vocabs check for AragoDBPedia took 0.4709632396697998s
Verifiability | Authors check for AragoDBPedia took 0.5276248455047607s
Verifiability | Publishers check for AragoDBPedia took 0.4309389591217041s
Performance | Throughput check for AragoDBPedia took 11.585936784744263s
Amount of data | Check the number of entities for AragoDBPedia took 7.295608520507812e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.526190996170044s
Interlinking | sameAs chians check for AragoDBPedia took 0.4662590026855469s
Interlinking | skos check for AragoDBPedia took 0.645442008972168s
Interlinking | skos check for AragoDBPedia took 0.36941075325012207s
Timeliness | dataset update frequency check for AragoDBPedia took 1.1753530502319336s
Currency | Creation date check for AragoDBPedia took 1.7765207290649414s
Currency | Modification date check for AragoDBPedia took 0.9014124870300293s
Rep.Conc. | URIs length for AragoDBPedia took 6.18207573890686s
Interoperability | New vocabularies check for AragoDBPedia took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.4037933349609375s
Accuracy | Check Functional Property for AragoDBPedia took 0.46477818489074707s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.5100643634796143s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.409874677658081s
Accuracy | Check White space in annotation for AragoDBPedia took 0.029936790466308594s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.0276033878326416s
Consistency | Disjoint class check for AragoDBPedia took 0.3976314067840576s
Consistency | Check Misplaced properties for AragoDBPedia took 4.755539178848267s
Consistency | Misplaced classes for AragoDBPedia took 0.72064208984375s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.812992572784424s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3581647872924805s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.644925832748413s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03419327735900879s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.6100137233734131s
Security | Sign check for AragoDBPedia took 0.5806055068969727s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3233.712406396866s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 0.65496826171875s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.02107715606689453s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBPedia took 5.7220458984375e-06s
INFO | --- Analysis for aragodbpedia took 11873.03820180893s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.14480233192444s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2597942352294922s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.030632019042969e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.62939453125e-06s
INFO | --- Analysis for archiveshub-linkeddata took 83.46475410461426s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.076957702636719e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.28290605545043945s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 2.7894973754882812e-05s
Believability | Calculation of trust value for Archivi ISMA took 6.67572021484375e-06s
INFO | --- Analysis for archivio-isma took 4.704256296157837s
Availability | SPARQL endpoint availability check for ARIADNE took 4.1484832763671875e-05s
Availability | VoID file availability check for ARIADNE took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2736856937408447s
Reputation | Calculation of the PageRank for ARIADNE took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 2.8133392333984375e-05s
Believability | Calculation of trust value for ARIADNE took 6.9141387939453125e-06s
INFO | --- Analysis for ariadne took 3.3497111797332764s
Availability | SPARQL endpoint availability check for Aristotle University took 5.412101745605469e-05s
Availability | VoID file availability check for Aristotle University took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.26277709007263184s
Reputation | Calculation of the PageRank for Aristotle University took 0.02019047737121582s
Interlinking | Calculation of Degree of Connection for Aristotle University took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 2.8371810913085938e-05s
Believability | Calculation of trust value for Aristotle University took 9.775161743164062e-06s
INFO | --- Analysis for aristotle-university took 3.756397008895874s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.967247724533081s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.27840518951416016s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.266334533691406e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 7.867813110351562e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.61995768547058s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.100799560546875e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.26005029678344727s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.075599670410156e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.1205673217773438e-05s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.8955469131469727s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.9119369983673096s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.00034427642822265625s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.2555861473083496s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.00543212890625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 6.67572021484375e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 17.763349294662476s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.26923513412475586s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020312070846557617s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010418891906738281s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 10.909674406051636s
Availability | SPARQL endpoint availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 4.220008850097656e-05s
Availability | VoID file availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.2675304412841797s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.020204782485961914s
Interlinking | Calculation of Degree of Connection for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0007326602935791016s
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 7.3909759521484375e-06s
INFO | --- Analysis for Arthron took 2.365999460220337s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.38690185546875e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0003294944763183594s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.24734020233154297s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 4.649162292480469e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.000102996826171875s
Believability | Calculation of trust value for Arthroscopy community took 7.3909759521484375e-06s
INFO | --- Analysis for arthroscopy took 33.96106791496277s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.8114452362060547s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0006372928619384766s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 28.35392165184021s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.518977165222168s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.16271328926086s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.1312146186828613s
Versatility | Languages check for Wikidata entry for Art × Science International took 60.22235465049744s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.1875946521759s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.47061634063720703s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.3690211772918701s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.43540096282958984s
License | MR license check for Wikidata entry for Art × Science International took 0.18998169898986816s
License | HR license check for Wikidata entry for Art × Science International took 65.18243861198425s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.5914490222930908s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.17338967323303s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.5944452285766602s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.2117018699645996s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.3342561721801758s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.18467998504638672s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 7.772445678710938e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.09243297576904297s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.08573031425476074s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.06996989250183105s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.0931997299194336s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.08132195472717285s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.15274620056152344s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.16289091110229492s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 3.8012094497680664s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.08088898658752441s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.6361165046691895s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.0814664363861084s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 0.08339905738830566s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 1.4364840984344482s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.8754069805145264s
Security | Sign check for Wikidata entry for Art × Science International took 0.06863999366760254s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 10.389222860336304s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.31163740158081055s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.8358230590820312e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.1920928955078125e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 7.62939453125e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 578.0057680606842s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.5083091259002686s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0003628730773925781s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2647883892059326s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.02070140838623047s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.416175842285156e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 14.087620496749878s
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.357149600982666s
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.0003612041473388672s
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.2523074150085449s
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.02040243148803711s
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.5497207641601562e-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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.581710815429688e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 11.49644660949707s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.3926467895507812s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0003769397735595703s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.28408360481262207s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.226799011230469e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 12.108173847198486s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.4056148529052734s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2737720012664795s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.482269287109375e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 6.198883056640625e-06s
INFO | --- Analysis for ASCDC-CRB took 14.33475375175476s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.3800227642059326s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.00038552284240722656s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.26525092124938965s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.988380432128906e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 6.198883056640625e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.660844087600708s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.4008543491363525s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2779207229614258s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.02076888084411621s
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.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.743171691894531e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 5.7220458984375e-06s
INFO | --- Analysis for ASCDC-DQOT took 12.830853939056396s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.3893699645996094s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.25423598289489746s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020835161209106445s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0008301734924316406s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.20159912109375e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 5.7220458984375e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.761597633361816s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.1662817001342773s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.2699580192565918s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.0108642578125e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 13.560869693756104s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.391946315765381s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.28315186500549316s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020921945571899414s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 7.271766662597656e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.593886375427246s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.3823187351226807s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2708561420440674s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.435943603515625e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.592217922210693s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.064443349838257s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2510349750518799s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.02127861976623535s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.935264587402344e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 16.11914873123169s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.416311264038086s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2634916305541992s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02131962776184082s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0011153221130371094s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.799003601074219e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 11.172757387161255s
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.4170634746551514s
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.0003941059112548828s
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.27495765686035156s
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.020766258239746094s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007317066192626953s
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 7.867813110351562e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.768208742141724s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.386650323867798s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.2673623561859131s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.458427429199219e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC_-_DNB took 11.052520990371704s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.2438507080078125e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2686944007873535s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020836830139160156s
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.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.677078247070312e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 6.9141387939453125e-06s
INFO | --- Analysis for asit took 7.909517288208008s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.315376281738281e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.26192355155944824s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.028133630752563477s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0008597373962402344s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.410743713378906e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 7.3909759521484375e-06s
INFO | --- Analysis for asjp took 5.471557855606079s
Availability | SPARQL endpoint availability check for ASN:US took 0.09483838081359863s
Availability | VoID file availability check for ASN:US took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2864253520965576s
Reputation | Calculation of the PageRank for ASN:US took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for ASN:US took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.67572021484375e-05s
Believability | Calculation of trust value for ASN:US took 5.245208740234375e-06s
INFO | --- Analysis for asn-us took 6.117150068283081s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.315376281738281e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.26033782958984375s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.0517578125e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 5.4836273193359375e-06s
INFO | --- Analysis for aspire-mmu took 4.333842039108276s
Availability | SPARQL endpoint availability check for associations took 4.220008850097656e-05s
Availability | VoID file availability check for associations took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for associations took 0.27984189987182617s
Reputation | Calculation of the PageRank for associations took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for associations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for associations took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for associations took 6.580352783203125e-05s
Believability | Calculation of trust value for associations took 9.775161743164062e-06s
INFO | --- Analysis for associations took 7.339332103729248s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.6253204345703125e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2868363857269287s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.8371810913085938e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 7.152557373046875e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.912997007369995s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.1961669921875e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.27029895782470703s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.131431579589844e-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 36.96752643585205s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 5.459785461425781e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.27184367179870605s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.858445644378662s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5450847148895264s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0007727146148681641s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.27147746086120605s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.507469177246094e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for AugustiniConfessiones took 3.974214553833008s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6080777645111084s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.29421138763427734s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.702278137207031e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 7.152557373046875e-06s
INFO | --- Analysis for austrian_ski_racers took 3.7955851554870605s
Availability | SPARQL endpoint availability check for AVsOnto took 4.2438507080078125e-05s
Availability | VoID file availability check for AVsOnto took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.2937343120574951s
Reputation | Calculation of the PageRank for AVsOnto took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for AVsOnto took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.170967102050781e-05s
Believability | Calculation of trust value for AVsOnto took 6.9141387939453125e-06s
INFO | --- Analysis for AVsOnto took 3.4370574951171875s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19505810737609863s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005218982696533203s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 200.04027462005615s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.483823299407959s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.053590297699s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 258.5269548892975s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0697376728058s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0850992202759s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.28534770011901855s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16906189918518066s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16601967811584473s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09909176826477051s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 45.973238945007324s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0762662887573s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15887880325317383s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 177.65754199028015s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22503066062927246s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09279441833496094s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12244796752929688s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09916424751281738s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.485658407211304s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.173683166503906e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09444141387939453s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0676181316376s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20760321617126465s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13354945182800293s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1259925365447998s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25937461853027344s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23865032196044922s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 362.98604941368103s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12460613250732422s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 13.66331148147583s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.2706215381622314s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.81080174446106s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12218070030212402s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.15844917297363s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 94.90794467926025s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.4720771312713623s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.5693156719208s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.8421919345855713s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15552234649658203s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.070451021194458s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.5530025959014893s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.020909547805786133s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.9073486328125e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.5299530029296875e-06s
INFO | --- Analysis for b3kat took 3912.770545721054s
Availability | SPARQL endpoint availability check for BabelNet took 0.5659902095794678s
Availability | VoID file availability check for BabelNet took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for BabelNet took 0.7383153438568115s
Reputation | Calculation of the PageRank for BabelNet took 0.020791292190551758s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001633167266845703s
Believability | Calculation of trust value for BabelNet took 6.67572021484375e-06s
INFO | --- Analysis for babelnet took 5.2691969871521s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.100799560546875e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.2695329189300537s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 2.956390380859375e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.049041748046875e-05s
INFO | --- Analysis for Bacevicius.lt took 3.292511224746704s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.4979431629180908s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2572970390319824s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.410743713378906e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 6.9141387939453125e-06s
INFO | --- Analysis for bag took 4.439512252807617s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.6111123561859131s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.7004597187042236s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.022045135498046875s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0008678436279296875s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.5762786865234375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 5.9604644775390625e-06s
INFO | --- Analysis for baixue took 4.702011585235596s
Availability | SPARQL endpoint availability check for baixue composer took 4.1961669921875e-05s
Availability | VoID file availability check for baixue composer took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for baixue composer took 0.3026893138885498s
Reputation | Calculation of the PageRank for baixue composer took 0.03202509880065918s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.52587890625e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0013003349304199219s
Interlinking | Calculation of Clustering coefficient for baixue composer took 4.8160552978515625e-05s
Believability | Calculation of trust value for baixue composer took 9.775161743164062e-06s
INFO | --- Analysis for baixue_composer took 3.188840866088867s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 5.793571472167969e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.25633883476257324s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.147125244140625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.4373016357421875e-06s
INFO | --- Analysis for baixue_imagery took 3.21761155128479s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 5.364418029785156e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.28040385246276855s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.266334533691406e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.198883056640625e-06s
INFO | --- Analysis for baixue_imagery1 took 3.64569354057312s
Availability | SPARQL endpoint availability check for BAMS took 4.076957702636719e-05s
Availability | VoID file availability check for BAMS took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for BAMS took 0.2639017105102539s
Reputation | Calculation of the PageRank for BAMS took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for BAMS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.24249267578125e-05s
Believability | Calculation of trust value for BAMS took 6.9141387939453125e-06s
INFO | --- Analysis for bams took 2.9561140537261963s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 5.1021575927734375e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.24924397468566895s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020892620086669922s
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.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.100799560546875e-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 3.0373313426971436s
Availability | SPARQL endpoint availability check for BBC Music took 0.4586458206176758s
Availability | VoID file availability check for BBC Music took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for BBC Music took 0.28560709953308105s
Reputation | Calculation of the PageRank for BBC Music took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001270771026611328s
Believability | Calculation of trust value for BBC Music took 6.9141387939453125e-06s
INFO | --- Analysis for bbc-music took 4.0115439891815186s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.2168560028076172s
Availability | VoID file availability check for BBC Programmes took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2680075168609619s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020838260650634766s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00011587142944335938s
Believability | Calculation of trust value for BBC Programmes took 5.9604644775390625e-06s
INFO | --- Analysis for bbc-programmes took 10.787172555923462s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.23941826820373535s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.26125359535217285s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020873546600341797s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010848045349121094s
Believability | Calculation of trust value for BBC Wildlife Finder took 7.152557373046875e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.402528047561646s
Availability | SPARQL endpoint availability check for BBOP took 4.220008850097656e-05s
Availability | VoID file availability check for BBOP took 0.0003590583801269531s
Completeness | Calculation of interlinking completeness for BBOP took 0.28443193435668945s
Reputation | Calculation of the PageRank for BBOP took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.814697265625e-05s
Believability | Calculation of trust value for BBOP took 6.9141387939453125e-06s
INFO | --- Analysis for bbop took 2.9729013442993164s
Availability | SPARQL endpoint availability check for BBOP took 6.914138793945312e-05s
Availability | VoID file availability check for BBOP took 0.0008273124694824219s
Completeness | Calculation of interlinking completeness for BBOP took 0.2689995765686035s
Reputation | Calculation of the PageRank for BBOP took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for BBOP took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.0994415283203125e-05s
Believability | Calculation of trust value for BBOP took 7.3909759521484375e-06s
INFO | --- Analysis for bbop-selected took 20.609506607055664s
Availability | SPARQL endpoint availability check for Bdgp took 1.9199161529541016s
Availability | VoID file availability check for Bdgp took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2633092403411865s
Reputation | Calculation of the PageRank for Bdgp took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.743171691894531e-05s
Believability | Calculation of trust value for Bdgp took 7.3909759521484375e-06s
INFO | --- Analysis for bdgp took 8.68523097038269s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.458427429199219e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.26700639724731445s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0009629726409912109s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.504753112792969e-05s
Believability | Calculation of trust value for Bendev Junior took 7.62939453125e-06s
INFO | --- Analysis for bendevoficial took 7.105751037597656s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.068169116973877s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.26343679428100586s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.914138793945312e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 4.5299530029296875e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 11.762500762939453s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.744529724121094e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.2789604663848877s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.021047353744506836s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.3855438232421875e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 7.867813110351562e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.8708338737487793s
Availability | SPARQL endpoint availability check for berlios took 4.363059997558594e-05s
Availability | VoID file availability check for berlios took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for berlios took 0.25539588928222656s
Reputation | Calculation of the PageRank for berlios took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for berlios took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for berlios took 8.702278137207031e-05s
Believability | Calculation of trust value for berlios took 6.9141387939453125e-06s
INFO | --- Analysis for berlios took 2.8030447959899902s
Availability | SPARQL endpoint availability check for Between Our Worlds took 5.888938903808594e-05s
Availability | VoID file availability check for Between Our Worlds took 0.00037479400634765625s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3218390941619873s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020754575729370117s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.05718994140625e-05s
Believability | Calculation of trust value for Between Our Worlds took 6.4373016357421875e-06s
INFO | --- Analysis for betweenourworlds took 9.253656387329102s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.4268033504486084s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.2699165344238281s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.083747863769531e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for bfs-linked-data took 2.941633939743042s
Availability | SPARQL endpoint availability check for BibBase took 0.0877237319946289s
Availability | VoID file availability check for BibBase took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for BibBase took 0.2881786823272705s
Reputation | Calculation of the PageRank for BibBase took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for BibBase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.489059448242188e-05s
Believability | Calculation of trust value for BibBase took 6.198883056640625e-06s
INFO | --- Analysis for bibbase took 2.4463586807250977s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.458427429199219e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0011630058288574219s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.26057982444763184s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.918212890625e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 7.253575563430786s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.315376281738281e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.26781702041625977s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.024349451065063477s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010395050048828125s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 8.106231689453125e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 9.22957706451416s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.076957702636719e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.2623622417449951s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.02206134796142578s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.361701965332031e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.9064841270446777s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.124641418457031e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2771146297454834s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.5762786865234375e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.1682510375976562e-05s
INFO | --- Analysis for BibSonomy took 9.485978603363037s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.220008850097656e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2620809078216553s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.0279159545898438e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 8.821487426757812e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 15.065052509307861s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.363059997558594e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2535114288330078s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020476102828979492s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007216930389404297s
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 1.1444091796875e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.52197527885437s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.26492929458618164s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.9075710773468018s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.2576045989990234s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005700588226318359s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 20.386423349380493s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.4957239627838135s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.70421528816223s
Interoperability | New terms check for Bio2RDF::Affymetrix took 43.03068566322327s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.12627172470093s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.14716458320617676s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.6095647811889648s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.24250149726867676s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 6.285473585128784s
License | MR license check for Bio2RDF::Affymetrix took 0.42836499214172363s
License | HR license check for Bio2RDF::Affymetrix took 60.095489501953125s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.1359260082244873s
Understandability | Number of label check for Bio2RDF::Affymetrix took 10.665534019470215s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.4150562286376953s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.1343522071838379s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.17049527168273926s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13149356842041016s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.723506450653076s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 73.09040236473083s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.6326491832733154s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.22671794891357422s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.8529808521270752s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.19368791580200195s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.10923266410827637s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.3065464496612549s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.2429828643798828s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 108.61295437812805s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 84.87755560874939s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.32660961151123047s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.14789414405822754s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.13654780387878418s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.413599491119385s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8855671882629395s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6782679557800293s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.33518028259277344s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.12230587005615s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.2590019702911377s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.471643924713135s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3258085250854492s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.41991400718689s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7263538837432861s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.4794778823852539s
Security | Sign check for Bio2RDF::Affymetrix took 0.12702417373657227s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 12.952577829360962s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.8098745346069336s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.0001068115234375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 232.370263338089s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1324.73073387146s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5178229808807373s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0007455348968505859s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.70821237564087s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.235393762588501s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 43.79833674430847s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.67317843437195s
Versatility | Languages check for Bio2RDF::Biomodels took 60.250224590301514s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2771928310394287s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.1707003116607666s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 1.1269116401672363s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.35010743141174316s
Availability | RDF dump link check for Bio2RDF::Biomodels took 6.409080743789673s
License | MR license check for Bio2RDF::Biomodels took 0.6121113300323486s
License | HR license check for Bio2RDF::Biomodels took 60.24586796760559s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.26288652420043945s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.890938997268677s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5875389575958252s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.25167417526245117s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.25592851638793945s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.2672548294067383s
Performance | Throughput check for Bio2RDF::Biomodels took 10.866022825241089s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 78.5860948562622s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.5745151042938232s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.3974003791809082s
Interlinking | skos check for Bio2RDF::Biomodels took 0.9509198665618896s
Interlinking | skos check for Bio2RDF::Biomodels took 0.35500049591064453s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2671487331390381s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5274336338043213s
Currency | Modification date check for Bio2RDF::Biomodels took 0.533005952835083s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 109.58351492881775s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 44.5729763507843s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.44159460067749023s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.2925293445587158s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.29836559295654297s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.71273946762085s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8902955055236816s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6591038703918457s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4832448959350586s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.3145387172699s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.417656660079956s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.291665554046631s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3089265823364258s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.534727811813354s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7124018669128418s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 1.4502174854278564s
Security | Sign check for Bio2RDF::Biomodels took 0.2751579284667969s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 12.250134468078613s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.8664388656616211s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.0001125335693359375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 46.55365610122681s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1111.3715267181396s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.5299530029296875e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.27300238609313965s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.838539123535156e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 4.768396854400635s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.4909698963165283s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006775856018066406s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.986019372940063s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2637205123901367s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 44.42486548423767s
Interoperability | New terms check for Bio2RDF::Bioportal took 44.490131855010986s
Versatility | Languages check for Bio2RDF::Bioportal took 60.243900537490845s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2680697441101074s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.14595389366149902s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 1.2620210647583008s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3408679962158203s
Availability | RDF dump link check for Bio2RDF::Bioportal took 6.488896369934082s
License | MR license check for Bio2RDF::Bioportal took 0.5845654010772705s
License | HR license check for Bio2RDF::Bioportal took 60.25553798675537s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2944931983947754s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.31889533996582s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5626981258392334s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.26014280319213867s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.26459836959838867s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.2563631534576416s
Performance | Throughput check for Bio2RDF::Bioportal took 11.497654438018799s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 77.45811128616333s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.7470700740814209s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3908107280731201s
Interlinking | skos check for Bio2RDF::Bioportal took 0.9355423450469971s
Interlinking | skos check for Bio2RDF::Bioportal took 0.35787057876586914s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.24827241897583008s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5058696269989014s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5178372859954834s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 108.50975060462952s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.41861534118652344s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.28332090377807617s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.274425745010376s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.666594743728638s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8828170299530029s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6533994674682617s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4644343852996826s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.02775979042053s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4111666679382324s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.816793441772461s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3146858215332031s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.579402446746826s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7040460109710693s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.4430530071258545s
Security | Sign check for Bio2RDF::Bioportal took 0.26204371452331543s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 12.252781629562378s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 1.5435454845428467s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020898103713989258s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004107952117919922s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-bioportal took 1041.699460029602s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.13983702659606934s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.25936436653137207s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.0201723575592041s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.173683166503906e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-chembl took 17.6857328414917s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.4609673023223877s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.000545501708984375s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 18.773013830184937s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2114489078521729s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 44.21038556098938s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 41.695706605911255s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.24342155456543s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.29248595237731934s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.1654984951019287s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 1.1050388813018799s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.35832738876342773s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 6.34368371963501s
License | MR license check for Bio2RDF::Clinicaltrials took 0.5694222450256348s
License | HR license check for Bio2RDF::Clinicaltrials took 60.26521158218384s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.26903772354125977s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.352888822555542s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5884242057800293s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.2620377540588379s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2679290771484375s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.27755236625671387s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 10.730885744094849s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 77.10289120674133s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 2.0387167930603027s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.4267139434814453s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 1.0676970481872559s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3535897731781006s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.24965786933898926s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5190269947052002s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5284759998321533s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 108.71125316619873s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 33.60131597518921s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.44873476028442383s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.29799628257751465s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2742786407470703s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 7.617770195007324s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8947513103485107s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6680545806884766s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.5249481201171875s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.33576846122742s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.442559242248535s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.655206680297852s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3470892906188965s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.58070182800293s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7075910568237305s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4369168281555176s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2728111743927002s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 12.410740375518799s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.8555645942687988s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.76837158203125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 28.860687017440796s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1079.068523645401s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.48325204849243164s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005924701690673828s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.82685112953186s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2308316230773926s
Amount of data | Number of triples check for Bio2RDF::Ctd took 44.09527611732483s
Interoperability | New terms check for Bio2RDF::Ctd took 43.72311091423035s
Versatility | Languages check for Bio2RDF::Ctd took 60.230895042419434s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2858445644378662s
Security | Check HTTPS for Bio2RDF::Ctd took 0.16575288772583008s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.8744292259216309s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.32637691497802734s
Availability | RDF dump link check for Bio2RDF::Ctd took 6.399751424789429s
License | MR license check for Bio2RDF::Ctd took 0.5372278690338135s
License | HR license check for Bio2RDF::Ctd took 60.24588942527771s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2709076404571533s
Understandability | Number of label check for Bio2RDF::Ctd took 10.543019533157349s
Understandability | URI regex check for Bio2RDF::Ctd took 0.6203451156616211s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.24943256378173828s
Verifiability | Authors check for Bio2RDF::Ctd took 0.26625752449035645s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.2599527835845947s
Performance | Throughput check for Bio2RDF::Ctd took 10.61936902999878s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 73.82242822647095s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.6146767139434814s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.42086124420166016s
Interlinking | skos check for Bio2RDF::Ctd took 1.1347301006317139s
Interlinking | skos check for Bio2RDF::Ctd took 0.33266735076904297s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.25278162956237793s
Currency | Creation date check for Bio2RDF::Ctd took 0.5204916000366211s
Currency | Modification date check for Bio2RDF::Ctd took 0.4929213523864746s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 109.61635112762451s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 34.940025091171265s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4501321315765381s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.29935169219970703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.26996278762817383s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.339977741241455s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8860452175140381s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.65519118309021s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.5080173015594482s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.1592104434967s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.4227242469787598s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.523738145828247s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3125147819519043s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.55845808982849s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7028865814208984s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.45184326171875s
Security | Sign check for Bio2RDF::Ctd took 0.27640867233276367s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 13.440523862838745s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 1.400233268737793s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.021149635314941406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0008585453033447266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 29.927908897399902s
Believability | Calculation of trust value for Bio2RDF::Ctd took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-ctd took 1091.3177452087402s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.363059997558594e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.7549731731414795s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.76837158203125e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-dataset took 4.453642845153809s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.47919321060180664s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005977153778076172s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 18.74471402168274s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2632958889007568s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 43.92135238647461s
Interoperability | New terms check for Bio2RDF::Dbsnp took 42.56646704673767s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.24890947341919s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.27860355377197266s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1560378074645996s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 1.0538761615753174s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.3586606979370117s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 6.419269323348999s
License | MR license check for Bio2RDF::Dbsnp took 0.5850040912628174s
License | HR license check for Bio2RDF::Dbsnp took 60.23944091796875s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2575044631958008s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.842381477355957s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5837125778198242s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.26213741302490234s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2586047649383545s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.2721431255340576s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.837394952774048s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 74.11050009727478s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 2.029331684112549s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.42331719398498535s
Interlinking | skos check for Bio2RDF::Dbsnp took 1.0298142433166504s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.33765339851379395s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.27150917053222656s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5480508804321289s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5409417152404785s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 109.12649488449097s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 46.75084614753723s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.41773343086242676s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2805032730102539s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2703738212585449s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.152074098587036s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8923158645629883s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6669578552246094s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.42516231536865234s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.19694876670837s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.4039804935455322s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.403160333633423s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.348973274230957s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.558743476867676s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7051081657409668s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.5784511566162109s
Security | Sign check for Bio2RDF::Dbsnp took 0.275998592376709s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 13.165307998657227s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.8654134273529053s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 53.69652438163757s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1117.2528800964355s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.48648548126220703s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006365776062011719s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 20.05004072189331s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.1999726295471191s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 44.14754271507263s
Interoperability | New terms check for Bio2RDF::Drugbank took 41.23621487617493s
Versatility | Languages check for Bio2RDF::Drugbank took 60.23921012878418s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.24800586700439453s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.15575289726257324s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.8744940757751465s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3356516361236572s
Availability | RDF dump link check for Bio2RDF::Drugbank took 6.432506084442139s
License | MR license check for Bio2RDF::Drugbank took 0.4483628273010254s
License | HR license check for Bio2RDF::Drugbank took 60.255733013153076s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.28574657440185547s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.33387041091919s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5787301063537598s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2634744644165039s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.27652907371520996s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2728457450866699s
Performance | Throughput check for Bio2RDF::Drugbank took 11.307206392288208s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 75.8418037891388s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.5799648761749268s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.37268710136413574s
Interlinking | skos check for Bio2RDF::Drugbank took 0.8803026676177979s
Interlinking | skos check for Bio2RDF::Drugbank took 0.3377542495727539s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2614312171936035s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5069067478179932s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5103645324707031s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 110.06905603408813s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 169.19039702415466s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4507596492767334s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.28760242462158203s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.25574421882629395s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.790363788604736s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8894927501678467s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6859390735626221s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.4039008617401123s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.30719184875488s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.6449146270751953s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.004872798919678s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.292923927307129s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.554375886917114s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7034099102020264s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.44971156120300293s
Security | Sign check for Bio2RDF::Drugbank took 0.27956342697143555s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 12.141145467758179s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 1.493837594985962s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020522594451904297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010704994201660156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 16.404086112976074s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1206.8875348567963s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.4770944118499756s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0005970001220703125s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.78615951538086s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2506067752838135s
Amount of data | Number of triples check for Bio2RDF::Genage took 43.72777223587036s
Interoperability | New terms check for Bio2RDF::Genage took 41.299896478652954s
Versatility | Languages check for Bio2RDF::Genage took 60.24120759963989s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2572903633117676s
Security | Check HTTPS for Bio2RDF::Genage took 0.1578197479248047s
Interpretability | RDF structures check for Bio2RDF::Genage took 1.1561737060546875s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.31565141677856445s
Availability | RDF dump link check for Bio2RDF::Genage took 6.330404996871948s
License | MR license check for Bio2RDF::Genage took 0.6446244716644287s
License | HR license check for Bio2RDF::Genage took 60.239959716796875s
Amount of data | Number of property check for Bio2RDF::Genage took 0.2622029781341553s
Understandability | Number of label check for Bio2RDF::Genage took 10.540555238723755s
Understandability | URI regex check for Bio2RDF::Genage took 0.5773360729217529s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2641892433166504s
Verifiability | Authors check for Bio2RDF::Genage took 0.27823781967163086s
Verifiability | Publishers check for Bio2RDF::Genage took 0.25433921813964844s
Performance | Throughput check for Bio2RDF::Genage took 10.826972246170044s
Amount of data | Check the number of entities for Bio2RDF::Genage took 73.67627882957458s
Verifiability | Contribs. check for Bio2RDF::Genage took 1.3455989360809326s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.713874340057373s
Interlinking | skos check for Bio2RDF::Genage took 0.8860619068145752s
Interlinking | skos check for Bio2RDF::Genage took 0.3401021957397461s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2674376964569092s
Currency | Creation date check for Bio2RDF::Genage took 0.53841233253479s
Currency | Modification date check for Bio2RDF::Genage took 0.4941983222961426s
Rep.Conc. | URIs length for Bio2RDF::Genage took 111.86972832679749s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.40313220024108887s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.29494428634643555s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.28729939460754395s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 8.31998324394226s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8902695178985596s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6671288013458252s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.3873908519744873s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.04683947563171s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.4141101837158203s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.777339458465576s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3087501525878906s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.523184299468994s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.707859992980957s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.4359138011932373s
Security | Sign check for Bio2RDF::Genage took 0.28340816497802734s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 12.190754175186157s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.8347125053405762s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.723403930664062e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-genage took 1024.3275384902954s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 7.939338684082031e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.6723151206970215s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.817413330078125e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-genbank took 4.156606197357178s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.4953455924987793s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0007460117340087891s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.771281242370605s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2626128196716309s
Amount of data | Number of triples check for Bio2RDF::Gendr took 43.42607879638672s
Interoperability | New terms check for Bio2RDF::Gendr took 41.82009553909302s
Versatility | Languages check for Bio2RDF::Gendr took 60.46978187561035s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2764449119567871s
Security | Check HTTPS for Bio2RDF::Gendr took 0.1467118263244629s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.8733179569244385s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.33950352668762207s
Availability | RDF dump link check for Bio2RDF::Gendr took 6.333039283752441s
License | MR license check for Bio2RDF::Gendr took 0.6706757545471191s
License | HR license check for Bio2RDF::Gendr took 60.24962115287781s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.27324700355529785s
Understandability | Number of label check for Bio2RDF::Gendr took 10.831869840621948s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5891745090484619s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.24483561515808105s
Verifiability | Authors check for Bio2RDF::Gendr took 0.26644110679626465s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.25736117362976074s
Performance | Throughput check for Bio2RDF::Gendr took 11.415163278579712s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 74.62442421913147s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.6057910919189453s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3822362422943115s
Interlinking | skos check for Bio2RDF::Gendr took 1.0660090446472168s
Interlinking | skos check for Bio2RDF::Gendr took 0.3735799789428711s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.25257015228271484s
Currency | Creation date check for Bio2RDF::Gendr took 0.5176832675933838s
Currency | Modification date check for Bio2RDF::Gendr took 0.5144383907318115s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 110.60255265235901s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 90.71819806098938s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.4477095603942871s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2861664295196533s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2964756488800049s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.456507921218872s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8957901000976562s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6713747978210449s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.43298888206481934s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.41467547416687s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.464810609817505s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.133959770202637s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.30112624168396s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.59078931808472s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7161848545074463s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.6121549606323242s
Security | Sign check for Bio2RDF::Gendr took 0.2822458744049072s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 12.746426820755005s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.537372350692749s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 65.30575847625732s
Believability | Calculation of trust value for Bio2RDF::Gendr took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-gendr took 1178.4506182670593s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4668865203857422s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006098747253417969s
Extra | Recovery of all triples for Bio2RDF::Goa took 20.366293907165527s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2282891273498535s
Amount of data | Number of triples check for Bio2RDF::Goa took 43.848114252090454s
Interoperability | New terms check for Bio2RDF::Goa took 40.87621593475342s
Versatility | Languages check for Bio2RDF::Goa took 60.23272776603699s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.27494382858276367s
Security | Check HTTPS for Bio2RDF::Goa took 0.1549990177154541s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.8752200603485107s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3409252166748047s
Availability | RDF dump link check for Bio2RDF::Goa took 6.3849029541015625s
License | MR license check for Bio2RDF::Goa took 0.5666525363922119s
License | HR license check for Bio2RDF::Goa took 60.25676393508911s
Amount of data | Number of property check for Bio2RDF::Goa took 0.3096625804901123s
Understandability | Number of label check for Bio2RDF::Goa took 10.822016716003418s
Understandability | URI regex check for Bio2RDF::Goa took 0.5553147792816162s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2510814666748047s
Verifiability | Authors check for Bio2RDF::Goa took 0.2758011817932129s
Verifiability | Publishers check for Bio2RDF::Goa took 0.26682281494140625s
Performance | Throughput check for Bio2RDF::Goa took 10.80663776397705s
Amount of data | Check the number of entities for Bio2RDF::Goa took 72.93730568885803s
Verifiability | Contribs. check for Bio2RDF::Goa took 1.374575138092041s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.38082289695739746s
Interlinking | skos check for Bio2RDF::Goa took 0.9397921562194824s
Interlinking | skos check for Bio2RDF::Goa took 0.3508584499359131s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2556166648864746s
Currency | Creation date check for Bio2RDF::Goa took 0.5556910037994385s
Currency | Modification date check for Bio2RDF::Goa took 0.514146089553833s
Rep.Conc. | URIs length for Bio2RDF::Goa took 109.5533938407898s
Interoperability | New vocabularies check for Bio2RDF::Goa took 104.32902956008911s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.44065237045288086s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2682180404663086s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.29456114768981934s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 8.102306365966797s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8858492374420166s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.7218706607818604s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4407162666320801s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.4483962059021s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.3823564052581787s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.019120693206787s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.2962183952331543s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 62.52753567695618s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7027816772460938s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.4679582118988037s
Security | Sign check for Bio2RDF::Goa took 0.2665283679962158s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 12.968987464904785s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.7506189346313477s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.02035069465637207s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 96.03633332252502s
Believability | Calculation of trust value for Bio2RDF::Goa took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-goa took 1225.245066165924s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.46617650985717773s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006036758422851562s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 19.504271745681763s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2022149562835693s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 44.22348594665527s
Interoperability | New terms check for Bio2RDF::Hgnc took 44.570982933044434s
Versatility | Languages check for Bio2RDF::Hgnc took 60.24737238883972s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2647383213043213s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.15611934661865234s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.7451386451721191s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.33830857276916504s
Availability | RDF dump link check for Bio2RDF::Hgnc took 6.446357250213623s
License | MR license check for Bio2RDF::Hgnc took 0.48298072814941406s
License | HR license check for Bio2RDF::Hgnc took 60.25788450241089s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2524392604827881s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.351462125778198s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5733048915863037s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.25127553939819336s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.2550065517425537s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.23914051055908203s
Performance | Throughput check for Bio2RDF::Hgnc took 11.01499080657959s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 73.63954710960388s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.589418888092041s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3578364849090576s
Interlinking | skos check for Bio2RDF::Hgnc took 0.8582539558410645s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3614463806152344s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.26227235794067383s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5308263301849365s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5277869701385498s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 110.18233060836792s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 54.3353374004364s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.43519020080566406s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2851850986480713s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.28495287895202637s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.445532321929932s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8901975154876709s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6658670902252197s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4248647689819336s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.38276791572571s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.390430212020874s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.612015247344971s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3131694793701172s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.53238320350647s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7104487419128418s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.6162326335906982s
Security | Sign check for Bio2RDF::Hgnc took 0.27022886276245117s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 12.929884433746338s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.9627599716186523s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02060079574584961s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00010418891906738281s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 83.14390420913696s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1158.587299823761s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 1.288116455078125s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0005710124969482422s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.733242750167847s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2758524417877197s
Amount of data | Number of triples check for Bio2RDF::Homologene took 44.37749218940735s
Interoperability | New terms check for Bio2RDF::Homologene took 45.66574549674988s
Versatility | Languages check for Bio2RDF::Homologene took 60.25642681121826s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2684473991394043s
Security | Check HTTPS for Bio2RDF::Homologene took 0.16785502433776855s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.7103531360626221s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.316500186920166s
Availability | RDF dump link check for Bio2RDF::Homologene took 6.425620794296265s
License | MR license check for Bio2RDF::Homologene took 0.49962759017944336s
License | HR license check for Bio2RDF::Homologene took 60.23987340927124s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.29316210746765137s
Understandability | Number of label check for Bio2RDF::Homologene took 10.861532926559448s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5979046821594238s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.26026487350463867s
Verifiability | Authors check for Bio2RDF::Homologene took 0.24607467651367188s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.25917768478393555s
Performance | Throughput check for Bio2RDF::Homologene took 11.247540473937988s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 72.56122350692749s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.7368626594543457s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.38463425636291504s
Interlinking | skos check for Bio2RDF::Homologene took 0.9202992916107178s
Interlinking | skos check for Bio2RDF::Homologene took 0.434067964553833s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.27097249031066895s
Currency | Creation date check for Bio2RDF::Homologene took 0.5132026672363281s
Currency | Modification date check for Bio2RDF::Homologene took 0.5368907451629639s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 110.33541965484619s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 63.293662548065186s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.45105743408203125s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2767207622528076s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.27979087829589844s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 6.9867753982543945s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8850977420806885s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6580517292022705s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.39448046684265137s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.29107880592346s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.377002239227295s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.3245744705200195s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3186330795288086s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.54702281951904s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7124559879302979s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.6018962860107422s
Security | Sign check for Bio2RDF::Homologene took 0.2911803722381592s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 11.895173788070679s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 1.3779606819152832s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.026729822158813477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 60.011701345443726s
Believability | Calculation of trust value for Bio2RDF::Homologene took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-homologene took 1143.2375221252441s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.2679173946380615s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-inoh took 2.8221096992492676s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.47742152214050293s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0005435943603515625s
Extra | Recovery of all triples for Bio2RDF::Interpro took 19.429142475128174s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2380831241607666s
Amount of data | Number of triples check for Bio2RDF::Interpro took 44.43448448181152s
Interoperability | New terms check for Bio2RDF::Interpro took 42.7980535030365s
Versatility | Languages check for Bio2RDF::Interpro took 60.27808380126953s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.25581955909729004s
Security | Check HTTPS for Bio2RDF::Interpro took 0.16463398933410645s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.7488424777984619s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.3254966735839844s
Availability | RDF dump link check for Bio2RDF::Interpro took 6.334978342056274s
License | MR license check for Bio2RDF::Interpro took 0.534259557723999s
License | HR license check for Bio2RDF::Interpro took 60.238118171691895s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.24404573440551758s
Understandability | Number of label check for Bio2RDF::Interpro took 10.359290599822998s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5879013538360596s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2625584602355957s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2608516216278076s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.27171921730041504s
Performance | Throughput check for Bio2RDF::Interpro took 10.758415937423706s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 75.37614965438843s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.5652751922607422s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.3916926383972168s
Interlinking | skos check for Bio2RDF::Interpro took 0.791522741317749s
Interlinking | skos check for Bio2RDF::Interpro took 0.3635430335998535s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2613551616668701s
Currency | Creation date check for Bio2RDF::Interpro took 0.5548090934753418s
Currency | Modification date check for Bio2RDF::Interpro took 0.5151746273040771s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 111.21659135818481s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 61.79124045372009s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4160478115081787s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2779812812805176s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2754333019256592s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.831038475036621s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.888167142868042s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6569972038269043s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.44173312187194824s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.13026332855225s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.4233713150024414s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.680279970169067s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3557140827178955s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.56553816795349s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.6980156898498535s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 1.4407694339752197s
Security | Sign check for Bio2RDF::Interpro took 0.27818822860717773s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 11.531092643737793s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.483565092086792s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010538101196289062s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 78.01519870758057s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-interpro took 1162.2231233119965s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.13260102272033691s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.6737675666809082s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020053863525390625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.82012939453125e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-iproclass took 16.804485082626343s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.47829651832580566s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006532669067382812s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 20.202876091003418s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.230473279953003s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.83308410644531s
Interoperability | New terms check for Bio2RDF::Irefindex took 41.35745978355408s
Versatility | Languages check for Bio2RDF::Irefindex took 60.26577806472778s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2576618194580078s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.1790480613708496s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.9554526805877686s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.30571603775024414s
Availability | RDF dump link check for Bio2RDF::Irefindex took 6.3876941204071045s
License | MR license check for Bio2RDF::Irefindex took 0.6059880256652832s
License | HR license check for Bio2RDF::Irefindex took 60.23709011077881s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.28531765937805176s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.227267742156982s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.6071643829345703s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2557828426361084s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.26886439323425293s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.25281500816345215s
Performance | Throughput check for Bio2RDF::Irefindex took 11.020727634429932s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 73.80098104476929s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.7149426937103271s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.38239502906799316s
Interlinking | skos check for Bio2RDF::Irefindex took 0.9770224094390869s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3628253936767578s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.26956892013549805s
Currency | Creation date check for Bio2RDF::Irefindex took 0.511533260345459s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5335941314697266s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 109.0947573184967s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 47.19443893432617s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.459000825881958s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2821049690246582s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.2987058162689209s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.1305131912231445s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8938021659851074s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6577932834625244s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.4250767230987549s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.05290818214417s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.41375732421875s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.694978713989258s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3594307899475098s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.606911420822144s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.71626877784729s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 1.0678489208221436s
Security | Sign check for Bio2RDF::Irefindex took 0.2970137596130371s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 12.750962257385254s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.4784669876098633s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.021212339401245117s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0008120536804199219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 9.393692016601562e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 67.85275173187256s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1128.4197285175323s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.4345855712890625e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.7098512649536133s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.341934204101562e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-kegg took 5.105798006057739s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.57763671875e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.2652320861816406s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.867154836654663s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13135242462158203s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2720348834991455s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 8.952354431152344s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.48658275604248047s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.00058746337890625s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.980902433395386s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2531232833862305s
Amount of data | Number of triples check for Bio2RDF::Lsr took 43.96947121620178s
Interoperability | New terms check for Bio2RDF::Lsr took 41.577391147613525s
Versatility | Languages check for Bio2RDF::Lsr took 60.25437641143799s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2806122303009033s
Security | Check HTTPS for Bio2RDF::Lsr took 0.1719956398010254s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.42302608489990234s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.2949645519256592s
Availability | RDF dump link check for Bio2RDF::Lsr took 6.3056371212005615s
License | MR license check for Bio2RDF::Lsr took 0.4388408660888672s
License | HR license check for Bio2RDF::Lsr took 60.24450206756592s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2721269130706787s
Understandability | Number of label check for Bio2RDF::Lsr took 10.071134567260742s
Understandability | URI regex check for Bio2RDF::Lsr took 0.6066441535949707s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.2657928466796875s
Verifiability | Authors check for Bio2RDF::Lsr took 0.28110194206237793s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.2628166675567627s
Performance | Throughput check for Bio2RDF::Lsr took 11.574944734573364s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 75.6683030128479s
Verifiability | Contribs. check for Bio2RDF::Lsr took 2.041208028793335s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3517725467681885s
Interlinking | skos check for Bio2RDF::Lsr took 1.0185327529907227s
Interlinking | skos check for Bio2RDF::Lsr took 0.347308874130249s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.26381993293762207s
Currency | Creation date check for Bio2RDF::Lsr took 0.5209877490997314s
Currency | Modification date check for Bio2RDF::Lsr took 0.5452075004577637s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 109.1340160369873s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 57.211496353149414s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4110109806060791s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.27985239028930664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2796447277069092s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.473260879516602s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8856444358825684s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6789724826812744s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.46663475036621094s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.66359877586365s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.4094443321228027s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.5176215171813965s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3028178215026855s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.53133845329285s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7064597606658936s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.5756826400756836s
Security | Sign check for Bio2RDF::Lsr took 0.263228178024292s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 12.105831861495972s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 1.4343678951263428s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020504236221313477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 54.52551889419556s
Believability | Calculation of trust value for Bio2RDF::Lsr took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-lsr took 1128.3391861915588s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.4762840270996094s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.000720977783203125s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.16582417488098s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.259045124053955s
Amount of data | Number of triples check for Bio2RDF::Mesh took 44.06316089630127s
Interoperability | New terms check for Bio2RDF::Mesh took 42.75497007369995s
Versatility | Languages check for Bio2RDF::Mesh took 60.259803771972656s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.2606661319732666s
Security | Check HTTPS for Bio2RDF::Mesh took 0.15771913528442383s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.5025722980499268s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.3336753845214844s
Availability | RDF dump link check for Bio2RDF::Mesh took 6.391839981079102s
License | MR license check for Bio2RDF::Mesh took 0.5323522090911865s
License | HR license check for Bio2RDF::Mesh took 60.24079751968384s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.28887009620666504s
Understandability | Number of label check for Bio2RDF::Mesh took 10.233417510986328s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5771000385284424s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2445697784423828s
Verifiability | Authors check for Bio2RDF::Mesh took 0.25539493560791016s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2715628147125244s
Performance | Throughput check for Bio2RDF::Mesh took 11.31235122680664s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 71.70915365219116s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.585235595703125s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.3783397674560547s
Interlinking | skos check for Bio2RDF::Mesh took 0.9904882907867432s
Interlinking | skos check for Bio2RDF::Mesh took 0.335430383682251s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.2627272605895996s
Currency | Creation date check for Bio2RDF::Mesh took 0.5520589351654053s
Currency | Modification date check for Bio2RDF::Mesh took 0.519601583480835s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 110.31682658195496s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 47.4289927482605s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.47379636764526367s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.28699302673339844s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2909362316131592s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.7244181632995605s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8921363353729248s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6593935489654541s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4330463409423828s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.14509582519531s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.3979439735412598s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.029388904571533s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.291548728942871s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.5030996799469s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6996960639953613s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.590437650680542s
Security | Sign check for Bio2RDF::Mesh took 0.25228238105773926s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 13.478909254074097s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.8461458683013916s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02791428565979004s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.653236389160156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 178.73538517951965s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-mesh took 1241.271380662918s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.47016477584838867s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0005939006805419922s
Extra | Recovery of all triples for Bio2RDF::Mgi took 19.847984075546265s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.232999324798584s
Amount of data | Number of triples check for Bio2RDF::Mgi took 44.492037534713745s
Interoperability | New terms check for Bio2RDF::Mgi took 42.17479968070984s
Versatility | Languages check for Bio2RDF::Mgi took 60.24117159843445s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.28362154960632324s
Security | Check HTTPS for Bio2RDF::Mgi took 0.15668487548828125s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.4242105484008789s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.31211352348327637s
Availability | RDF dump link check for Bio2RDF::Mgi took 6.440082550048828s
License | MR license check for Bio2RDF::Mgi took 0.4632406234741211s
License | HR license check for Bio2RDF::Mgi took 60.25310969352722s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.24596166610717773s
Understandability | Number of label check for Bio2RDF::Mgi took 10.314179182052612s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5923442840576172s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.26801252365112305s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2522122859954834s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.26058197021484375s
Performance | Throughput check for Bio2RDF::Mgi took 11.431272268295288s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 76.13061761856079s
Verifiability | Contribs. check for Bio2RDF::Mgi took 2.0420923233032227s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.40265536308288574s
Interlinking | skos check for Bio2RDF::Mgi took 0.926133394241333s
Interlinking | skos check for Bio2RDF::Mgi took 0.3533344268798828s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.28394412994384766s
Currency | Creation date check for Bio2RDF::Mgi took 0.5404331684112549s
Currency | Modification date check for Bio2RDF::Mgi took 0.5029160976409912s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 109.27385139465332s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.4318122863769531s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.26938414573669434s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2668640613555908s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 6.951619863510132s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8901286125183105s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6689586639404297s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.3574409484863281s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.24884700775146s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.45977783203125s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.09780216217041s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.2942025661468506s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.503069162368774s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7104809284210205s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.4358382225036621s
Security | Sign check for Bio2RDF::Mgi took 0.2847011089324951s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 11.542805910110474s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.5440587997436523s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.584426879882812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 84.172682762146s
Believability | Calculation of trust value for Bio2RDF::Mgi took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-mgi took 1115.7933712005615s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.48076295852661133s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006260871887207031s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 18.633759021759033s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.276679515838623s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.37491226196289s
Interoperability | New terms check for Bio2RDF::Ncbigene took 42.80847430229187s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.24923253059387s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2552180290222168s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.16701269149780273s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.9399306774139404s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3436856269836426s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 6.474948167800903s
License | MR license check for Bio2RDF::Ncbigene took 0.4877631664276123s
License | HR license check for Bio2RDF::Ncbigene took 60.236674308776855s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.25472354888916016s
Understandability | Number of label check for Bio2RDF::Ncbigene took 10.281163454055786s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.589916467666626s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.2540721893310547s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2830698490142822s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2708749771118164s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.488506317138672s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 75.07063555717468s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.6265983581542969s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.38815879821777344s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.8712592124938965s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3468482494354248s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2593808174133301s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.527087926864624s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5290305614471436s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 108.41694450378418s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 41.341686487197876s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.41892266273498535s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2828841209411621s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.280367374420166s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.693162441253662s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8856966495513916s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6973943710327148s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.37392401695251465s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.75684261322021s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.5191054344177246s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.764530658721924s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.2910332679748535s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.53099036216736s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.712205171585083s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.6304380893707275s
Security | Sign check for Bio2RDF::Ncbigene took 0.2746908664703369s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 11.77068042755127s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 1.2909331321716309s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011467933654785156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 33.868218660354614s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1097.5255270004272s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.47105908393859863s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0003581047058105469s
Extra | Recovery of all triples for Bio2RDF::Ndc took 19.70398998260498s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2243807315826416s
Amount of data | Number of triples check for Bio2RDF::Ndc took 44.830318212509155s
Interoperability | New terms check for Bio2RDF::Ndc took 44.2899169921875s
Versatility | Languages check for Bio2RDF::Ndc took 60.24865126609802s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2505791187286377s
Security | Check HTTPS for Bio2RDF::Ndc took 0.14559388160705566s
Interpretability | RDF structures check for Bio2RDF::Ndc took 1.0760142803192139s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.36980605125427246s
Availability | RDF dump link check for Bio2RDF::Ndc took 6.552877187728882s
License | MR license check for Bio2RDF::Ndc took 0.47307896614074707s
License | HR license check for Bio2RDF::Ndc took 60.25382924079895s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2938110828399658s
Understandability | Number of label check for Bio2RDF::Ndc took 11.386792421340942s
Understandability | URI regex check for Bio2RDF::Ndc took 0.6135420799255371s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2647099494934082s
Verifiability | Authors check for Bio2RDF::Ndc took 0.26364707946777344s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.25167346000671387s
Performance | Throughput check for Bio2RDF::Ndc took 11.033813714981079s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 78.42834877967834s
Verifiability | Contribs. check for Bio2RDF::Ndc took 1.8696916103363037s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.3868708610534668s
Interlinking | skos check for Bio2RDF::Ndc took 0.8327803611755371s
Interlinking | skos check for Bio2RDF::Ndc took 0.3760960102081299s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.24982023239135742s
Currency | Creation date check for Bio2RDF::Ndc took 0.527717113494873s
Currency | Modification date check for Bio2RDF::Ndc took 0.5194711685180664s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 111.26644134521484s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 47.35275888442993s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.458341121673584s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.28968071937561035s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2815983295440674s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.667037010192871s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8856170177459717s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6668403148651123s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.42380785942077637s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.22605633735657s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.405566692352295s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.641417741775513s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3339076042175293s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.54625844955444s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7222304344177246s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.5500533580780029s
Security | Sign check for Bio2RDF::Ndc took 0.2668800354003906s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 11.697420835494995s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.9594898223876953s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 67.93106842041016s
Believability | Calculation of trust value for Bio2RDF::Ndc took 3.528594970703125e-05s
INFO | --- Analysis for bio2rdf-ndc took 1142.1995768547058s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.2505812644958496s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020714998245239258s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-netpath took 4.598278760910034s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13033509254455566s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.00030803680419921875s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2746288776397705s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02008533477783203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-nextprot took 3.324002504348755s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.4661130905151367s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006353855133056641s
Extra | Recovery of all triples for Bio2RDF::Omim took 19.009113788604736s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.227518081665039s
Amount of data | Number of triples check for Bio2RDF::Omim took 44.25724148750305s
Interoperability | New terms check for Bio2RDF::Omim took 42.178563594818115s
Versatility | Languages check for Bio2RDF::Omim took 60.26284122467041s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2776176929473877s
Security | Check HTTPS for Bio2RDF::Omim took 0.1564633846282959s
Interpretability | RDF structures check for Bio2RDF::Omim took 1.3186020851135254s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.3247392177581787s
Availability | RDF dump link check for Bio2RDF::Omim took 6.538763999938965s
License | MR license check for Bio2RDF::Omim took 0.4603414535522461s
License | HR license check for Bio2RDF::Omim took 60.251625299453735s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2695956230163574s
Understandability | Number of label check for Bio2RDF::Omim took 10.92909288406372s
Understandability | URI regex check for Bio2RDF::Omim took 0.584418773651123s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2505202293395996s
Verifiability | Authors check for Bio2RDF::Omim took 0.25730395317077637s
Verifiability | Publishers check for Bio2RDF::Omim took 0.27124571800231934s
Performance | Throughput check for Bio2RDF::Omim took 11.00263524055481s
Amount of data | Check the number of entities for Bio2RDF::Omim took 77.86729025840759s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.5989656448364258s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3516874313354492s
Interlinking | skos check for Bio2RDF::Omim took 0.8570809364318848s
Interlinking | skos check for Bio2RDF::Omim took 0.36119771003723145s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.2583436965942383s
Currency | Creation date check for Bio2RDF::Omim took 0.5150852203369141s
Currency | Modification date check for Bio2RDF::Omim took 0.534285306930542s
Rep.Conc. | URIs length for Bio2RDF::Omim took 112.19302582740784s
Interoperability | New vocabularies check for Bio2RDF::Omim took 67.0095443725586s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.403597354888916s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.28968191146850586s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.27689647674560547s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 8.034954071044922s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8950212001800537s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6877517700195312s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.42114806175231934s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.50660061836243s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.408329725265503s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.542744874954224s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3329999446868896s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.536935329437256s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7097032070159912s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.6213119029998779s
Security | Sign check for Bio2RDF::Omim took 0.2834608554840088s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 11.2654128074646s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 1.272390604019165s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020856380462646484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00015854835510253906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 53.204978704452515s
Believability | Calculation of trust value for Bio2RDF::Omim took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-omim took 1144.621797323227s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.410743713378906e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.708204984664917s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020282506942749023s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.790855407714844e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 3.0517578125e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 4.056192636489868s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.47376370429992676s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0005924701690673828s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 19.329641580581665s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2628016471862793s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 44.86502146720886s
Interoperability | New terms check for Bio2RDF::Orphanet took 41.40229368209839s
Versatility | Languages check for Bio2RDF::Orphanet took 60.26130294799805s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.26941728591918945s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.15745067596435547s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 1.277346134185791s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.3410172462463379s
Availability | RDF dump link check for Bio2RDF::Orphanet took 6.419771671295166s
License | MR license check for Bio2RDF::Orphanet took 0.6372785568237305s
License | HR license check for Bio2RDF::Orphanet took 60.25562524795532s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.2931044101715088s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.304632902145386s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5764880180358887s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.25103092193603516s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.28934717178344727s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2661759853363037s
Performance | Throughput check for Bio2RDF::Orphanet took 11.470994472503662s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 77.82662677764893s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 2.028456211090088s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.39006567001342773s
Interlinking | skos check for Bio2RDF::Orphanet took 0.9761795997619629s
Interlinking | skos check for Bio2RDF::Orphanet took 0.330655574798584s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.28232693672180176s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5349252223968506s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5225260257720947s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 109.36338233947754s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 44.524816036224365s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.46059370040893555s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.28115105628967285s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2719740867614746s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.969649314880371s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8876101970672607s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6542537212371826s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.4216737747192383s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.67678475379944s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.3874311447143555s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 5.92448091506958s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3062644004821777s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.57916474342346s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7276701927185059s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.5667612552642822s
Security | Sign check for Bio2RDF::Orphanet took 0.27259111404418945s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 12.16079330444336s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 1.0238301753997803s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 7.200241088867188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 35.57790946960449s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1105.2924704551697s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.13890933990478516s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.255781888961792s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 10.182165145874023s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 1.2766129970550537s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006880760192871094s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.455390453338623s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.206636905670166s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 44.07218074798584s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 41.11694526672363s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.26473927497864s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2708628177642822s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.14561963081359863s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.83294677734375s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.34838247299194336s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 6.458979606628418s
License | MR license check for Bio2RDF::Pharmgkb took 0.512535572052002s
License | HR license check for Bio2RDF::Pharmgkb took 60.23802351951599s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2595856189727783s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.313334465026855s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.569683313369751s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.248948335647583s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.260739803314209s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2474074363708496s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.304147243499756s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 76.11263298988342s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.5912532806396484s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.39481186866760254s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.7601823806762695s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.4061257839202881s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.26857686042785645s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5270900726318359s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5235714912414551s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 109.3464732170105s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 21.289141416549683s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4069342613220215s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.27132105827331543s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.2777421474456787s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.462726593017578s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.884986162185669s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6802661418914795s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4490513801574707s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 64.89128875732422s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4124996662139893s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.412535905838013s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3147494792938232s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.53601431846619s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7127528190612793s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4328186511993408s
Security | Sign check for Bio2RDF::Pharmgkb took 0.2648146152496338s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 11.585072994232178s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.3047499656677246s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 56.61921572685242s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 3.24249267578125e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1101.0852892398834s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2562694549560547s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.227708101272583s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.248582124710083s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020138978958129883s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 2.8133392333984375e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-pid took 3.3317172527313232s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 5.2928924560546875e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.3018224239349365s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 2.9740710258483887s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.46455812454223633s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0005497932434082031s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 19.581758737564087s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2692201137542725s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 44.13560628890991s
Interoperability | New terms check for Bio2RDF::Pubmed took 46.02591681480408s
Versatility | Languages check for Bio2RDF::Pubmed took 60.24595236778259s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.26505255699157715s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.16965579986572266s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.5962367057800293s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3458542823791504s
Availability | RDF dump link check for Bio2RDF::Pubmed took 6.468719959259033s
License | MR license check for Bio2RDF::Pubmed took 0.49237608909606934s
License | HR license check for Bio2RDF::Pubmed took 60.25978064537048s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2660698890686035s
Understandability | Number of label check for Bio2RDF::Pubmed took 10.182171106338501s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.605975866317749s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2577540874481201s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2533230781555176s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.25543713569641113s
Performance | Throughput check for Bio2RDF::Pubmed took 11.084933996200562s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 74.08018136024475s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 2.0328099727630615s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3587968349456787s
Interlinking | skos check for Bio2RDF::Pubmed took 0.775360107421875s
Interlinking | skos check for Bio2RDF::Pubmed took 0.34286022186279297s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.25043654441833496s
Currency | Creation date check for Bio2RDF::Pubmed took 0.513089656829834s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5288662910461426s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 109.82453107833862s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 69.1153633594513s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.45320987701416016s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.25960659980773926s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.28633952140808105s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.771510601043701s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8816511631011963s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6601109504699707s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.6435434818267822s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.34903383255005s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.4548745155334473s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.604549884796143s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3572933673858643s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.54213905334473s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7137618064880371s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 1.393744945526123s
Security | Sign check for Bio2RDF::Pubmed took 0.28313374519348145s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 14.018381357192993s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.5770249366760254s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020287275314331055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013756752014160156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 38.428383350372314s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1131.6770322322845s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.24606037139892578s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 7.581710815429688e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-reactome took 4.265198230743408s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.2397937774658203s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.53131103515625e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.758166790008545s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.13481593132019043s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.25394296646118164s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.748603820800781e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sabiork took 9.946703910827637s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.469585657119751s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0006604194641113281s
Extra | Recovery of all triples for Bio2RDF::Sgd took 19.086177825927734s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2627968788146973s
Amount of data | Number of triples check for Bio2RDF::Sgd took 44.07208776473999s
Interoperability | New terms check for Bio2RDF::Sgd took 42.821428060531616s
Versatility | Languages check for Bio2RDF::Sgd took 60.247604846954346s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.24307489395141602s
Security | Check HTTPS for Bio2RDF::Sgd took 0.16566181182861328s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.7180354595184326s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.34975695610046387s
Availability | RDF dump link check for Bio2RDF::Sgd took 6.365015268325806s
License | MR license check for Bio2RDF::Sgd took 0.6105923652648926s
License | HR license check for Bio2RDF::Sgd took 60.27740001678467s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.29044055938720703s
Understandability | Number of label check for Bio2RDF::Sgd took 10.472176313400269s
Understandability | URI regex check for Bio2RDF::Sgd took 0.6058218479156494s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2619435787200928s
Verifiability | Authors check for Bio2RDF::Sgd took 0.26448750495910645s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.2532777786254883s
Performance | Throughput check for Bio2RDF::Sgd took 11.553836584091187s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 74.13237524032593s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.5838992595672607s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.34143495559692383s
Interlinking | skos check for Bio2RDF::Sgd took 0.9901711940765381s
Interlinking | skos check for Bio2RDF::Sgd took 0.4213399887084961s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2489173412322998s
Currency | Creation date check for Bio2RDF::Sgd took 0.5107450485229492s
Currency | Modification date check for Bio2RDF::Sgd took 0.5075247287750244s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 109.14917206764221s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 67.9195454120636s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.4795999526977539s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2878856658935547s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.27617907524108887s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 7.508291006088257s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8855855464935303s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.670341968536377s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.4394650459289551s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.27685928344727s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4449801445007324s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.472500801086426s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3126757144927979s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.57015323638916s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7026541233062744s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.5796241760253906s
Security | Sign check for Bio2RDF::Sgd took 0.27866196632385254s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 13.647516012191772s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.35089969635009766s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010395050048828125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 64.7726137638092s
Believability | Calculation of trust value for Bio2RDF::Sgd took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-sgd took 1147.8289396762848s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.3392181396484375e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.2506980895996094s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020074844360351562s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.6716461181640625e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 3.5956075191497803s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.4850423336029053s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0007371902465820312s
Extra | Recovery of all triples for Bio2RDF::Sider took 20.61118984222412s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2111046314239502s
Amount of data | Number of triples check for Bio2RDF::Sider took 43.701056480407715s
Interoperability | New terms check for Bio2RDF::Sider took 41.68145728111267s
Versatility | Languages check for Bio2RDF::Sider took 60.267677783966064s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.2687242031097412s
Security | Check HTTPS for Bio2RDF::Sider took 0.15549325942993164s
Interpretability | RDF structures check for Bio2RDF::Sider took 1.164050817489624s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3537459373474121s
Availability | RDF dump link check for Bio2RDF::Sider took 6.40067720413208s
License | MR license check for Bio2RDF::Sider took 0.6338200569152832s
License | HR license check for Bio2RDF::Sider took 60.239880323410034s
Amount of data | Number of property check for Bio2RDF::Sider took 0.2648916244506836s
Understandability | Number of label check for Bio2RDF::Sider took 10.627363204956055s
Understandability | URI regex check for Bio2RDF::Sider took 0.5801894664764404s
Understandability | Vocabs check for Bio2RDF::Sider took 0.2694263458251953s
Verifiability | Authors check for Bio2RDF::Sider took 0.2567925453186035s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2498941421508789s
Performance | Throughput check for Bio2RDF::Sider took 11.790374755859375s
Amount of data | Check the number of entities for Bio2RDF::Sider took 75.51854801177979s
Verifiability | Contribs. check for Bio2RDF::Sider took 2.0722055435180664s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.40389180183410645s
Interlinking | skos check for Bio2RDF::Sider took 0.9293410778045654s
Interlinking | skos check for Bio2RDF::Sider took 0.3904540538787842s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2915985584259033s
Currency | Creation date check for Bio2RDF::Sider took 0.5225996971130371s
Currency | Modification date check for Bio2RDF::Sider took 0.5190913677215576s
Rep.Conc. | URIs length for Bio2RDF::Sider took 112.08550095558167s
Interoperability | New vocabularies check for Bio2RDF::Sider took 51.688369274139404s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.427440881729126s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.29453468322753906s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2898073196411133s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.013431072235107s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8823306560516357s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.651862382888794s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.435333251953125s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.08697295188904s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.4139628410339355s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 7.145793199539185s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.339813470840454s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.56214904785156s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7144455909729004s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.6006207466125488s
Security | Sign check for Bio2RDF::Sider took 0.2856581211090088s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 13.772111654281616s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 1.3937358856201172s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 86.77201056480408s
Believability | Calculation of trust value for Bio2RDF::Sider took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-sider took 1166.4045460224152s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.2749452590942383s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-spike took 5.7506959438323975s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.458427429199219e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.7040293216705322s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.076957702636719e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-taxon took 3.5157008171081543s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.4764571189880371s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006358623504638672s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 20.10410761833191s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.489593267440796s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 43.72682309150696s
Interoperability | New terms check for Bio2RDF::Taxonomy took 42.30266332626343s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.25699973106384s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.28880834579467773s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.15664005279541016s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.9972724914550781s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.33574891090393066s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 6.39943790435791s
License | MR license check for Bio2RDF::Taxonomy took 0.5228922367095947s
License | HR license check for Bio2RDF::Taxonomy took 60.23313927650452s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.28984785079956055s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.070161819458008s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5895378589630127s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2564816474914551s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.278515100479126s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2551140785217285s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.360435724258423s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 79.01533436775208s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.5511629581451416s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3623828887939453s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.9088864326477051s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.33770108222961426s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2555098533630371s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.512850284576416s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5315732955932617s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 108.59577178955078s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 70.29093360900879s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4289743900299072s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.28245043754577637s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2909853458404541s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 7.421786069869995s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8948581218719482s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6872265338897705s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.5049796104431152s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.32039284706116s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.387859582901001s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.841246128082275s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3078041076660156s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.557902574539185s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.708158016204834s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.5794665813446045s
Security | Sign check for Bio2RDF::Taxonomy took 0.3003983497619629s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 11.36390233039856s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.44583559036254883s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.000102996826171875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 109.39222359657288s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1202.8547365665436s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.1428370475769043s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.2668321132659912s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 18.06061363220215s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4744284152984619s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006165504455566406s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 19.395259380340576s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2600586414337158s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 44.21425104141235s
Interoperability | New terms check for Bio2RDF::Wormbase took 41.9328351020813s
Versatility | Languages check for Bio2RDF::Wormbase took 60.23845100402832s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.28763508796691895s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.16797184944152832s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.8901917934417725s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3225829601287842s
Availability | RDF dump link check for Bio2RDF::Wormbase took 6.411563873291016s
License | MR license check for Bio2RDF::Wormbase took 0.46158337593078613s
License | HR license check for Bio2RDF::Wormbase took 60.259244203567505s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2582542896270752s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.220519781112671s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.574289083480835s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2582383155822754s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2708251476287842s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.2582817077636719s
Performance | Throughput check for Bio2RDF::Wormbase took 11.02163815498352s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 73.88810515403748s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.7576189041137695s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.38097620010375977s
Interlinking | skos check for Bio2RDF::Wormbase took 1.0207717418670654s
Interlinking | skos check for Bio2RDF::Wormbase took 0.36347174644470215s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2729911804199219s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5200364589691162s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5278971195220947s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 109.75234341621399s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 74.61097311973572s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.40067028999328613s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.28093791007995605s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.28864550590515137s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 7.278074741363525s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8825023174285889s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6536645889282227s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.404526948928833s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.12163782119751s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.421548843383789s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.160010099411011s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3045425415039062s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.57473587989807s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7210743427276611s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.6171350479125977s
Security | Sign check for Bio2RDF::Wormbase took 0.2747318744659424s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 11.96761178970337s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.4932734966278076s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 9.1552734375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 88.0924801826477s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1181.4698338508606s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.57763671875e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.7512164115905762s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.02021002769470215s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.2874603271484375e-05s
Believability | Calculation of trust value for Biografías y Vidas took 6.4373016357421875e-06s
INFO | --- Analysis for biografiasyvidas took 3.3514163494110107s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.24201345443725586s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.7302212715148926s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.654594421386719e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 5.245208740234375e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.625545024871826s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.25534749031066895s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.02039027214050293s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007359981536865234s
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.62939453125e-06s
INFO | --- Analysis for biolit took 2.9130260944366455s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.506111145019531e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0011444091796875s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.3317534923553467s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.02082061767578125s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.9577484130859375e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 7.152557373046875e-06s
INFO | --- Analysis for biolod-pdb took 7.91197943687439s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.5717403888702393s
Availability | VoID file availability check for BioModels RDF took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2557637691497803s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for BioModels RDF took 1.1444091796875e-05s
INFO | --- Analysis for biomodels-rdf took 3.539172887802124s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.960238456726074s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2552952766418457s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.67572021484375e-06s
INFO | --- Analysis for Biop took 8.397786617279053s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.152557373046875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2603588104248047s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.337860107421875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 6.9141387939453125e-06s
INFO | --- Analysis for Bioportal took 2.4127938747406006s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.28913354873657227s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006082057952880859s
Believability | Calculation of trust value for Amphibian gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-aao took 2.806633234024048s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.601478576660156e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.28200221061706543s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02400064468383789s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0012447834014892578s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0004076957702636719s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-aba took 2.7032289505004883s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.27242207527160645s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020605802536010742s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015225410461425781s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-acgt took 3.1867377758026123s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.291534423828125e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.2779819965362549s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.00032639503479003906s
Believability | Calculation of trust value for Animal natural history and life history took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-adw took 2.6564180850982666s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.25009608268737793s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004584789276123047s
Believability | Calculation of trust value for Anatomical Entity Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-aeo took 2.5763494968414307s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.282062292098999s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02035379409790039s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009570121765136719s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-aero took 2.606600522994995s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.1961669921875e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.25089526176452637s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020218849182128906s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00039458274841308594s
Believability | Calculation of trust value for AI/RHEUM took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-air took 2.5837783813476562s
Availability | SPARQL endpoint availability check for Amino Acid took 5.459785461425781e-05s
Availability | VoID file availability check for Amino Acid took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.24196600914001465s
Reputation | Calculation of the PageRank for Amino Acid took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for Amino Acid took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.000263214111328125s
Believability | Calculation of trust value for Amino Acid took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.5974550247192383s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.26656556129455566s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00030541419982910156s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-apo took 2.6394288539886475s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.1484832763671875e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.3016061782836914s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00023055076599121094s
Believability | Calculation of trust value for African Traditional Medicine took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-atmo took 2.635737419128418s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 5.507469177246094e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.25676989555358887s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02117133140563965s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.1552734375e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ato took 2.6683833599090576s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.24790024757385254s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013017654418945312s
Believability | Calculation of trust value for BioAssay Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bao took 2.6484570503234863s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2721283435821533s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003743171691894531s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.6670920848846436s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.26923036575317383s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020287036895751953s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003120899200439453s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bcgo took 2.6126556396484375s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.25661373138427734s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020327329635620117s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013930797576904297s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bdo took 2.546642780303955s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.25644350051879883s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020241260528564453s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004851818084716797s
Believability | Calculation of trust value for Basic Formal Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bfo took 2.6202638149261475s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.1961669921875e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2681417465209961s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02023148536682129s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007281303405761719s
Believability | Calculation of trust value for Bleeding History Phenotype took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bho took 2.623905658721924s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.26479458808898926s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020286083221435547s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004489421844482422s
Believability | Calculation of trust value for Bilateria anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-bila took 2.610847234725952s
Availability | SPARQL endpoint availability check for BIRNLex took 4.220008850097656e-05s
Availability | VoID file availability check for BIRNLex took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.28954648971557617s
Reputation | Calculation of the PageRank for BIRNLex took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for BIRNLex took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014998912811279297s
Believability | Calculation of trust value for BIRNLex took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-birnlex took 2.630934238433838s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2623133659362793s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007429122924804688s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.58506441116333s
Availability | SPARQL endpoint availability check for BioPAX took 4.220008850097656e-05s
Availability | VoID file availability check for BioPAX took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for BioPAX took 0.26697373390197754s
Reputation | Calculation of the PageRank for BioPAX took 0.023599624633789062s
Interlinking | Calculation of Degree of Connection for BioPAX took 5.221366882324219e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0010988712310791016s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.0001270771026611328s
Believability | Calculation of trust value for BioPAX took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bp took 2.5688862800598145s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.28192663192749023s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00032830238342285156s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.656445264816284s
Availability | SPARQL endpoint availability check for Spatial Ontology took 7.390975952148438e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.26743149757385254s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.021739482879638672s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00021123886108398438s
Believability | Calculation of trust value for Spatial Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-bspo took 2.568619966506958s
Availability | SPARQL endpoint availability check for BioTop took 4.2438507080078125e-05s
Availability | VoID file availability check for BioTop took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for BioTop took 0.24111294746398926s
Reputation | Calculation of the PageRank for BioTop took 0.020165443420410156s
Interlinking | Calculation of Degree of Connection for BioTop took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioTop took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006513595581054688s
Believability | Calculation of trust value for BioTop took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bt took 2.6028032302856445s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.2438507080078125e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.25771355628967285s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.02144932746887207s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0009980201721191406s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0009660720825195312s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-bto took 2.579253673553467s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.2950587272644043s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020276784896850586s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018138885498046875s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-canco took 3.0334649085998535s
Availability | SPARQL endpoint availability check for CAO took 4.172325134277344e-05s
Availability | VoID file availability check for CAO took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for CAO took 0.28653502464294434s
Reputation | Calculation of the PageRank for CAO took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for CAO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005972385406494141s
Believability | Calculation of trust value for CAO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cao took 2.7231788635253906s
Availability | SPARQL endpoint availability check for CareLex took 4.2438507080078125e-05s
Availability | VoID file availability check for CareLex took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for CareLex took 0.28786730766296387s
Reputation | Calculation of the PageRank for CareLex took 0.02027130126953125s
Interlinking | Calculation of Degree of Connection for CareLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.030632019042969e-05s
Believability | Calculation of trust value for CareLex took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-carelex took 2.623412847518921s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.24841046333312988s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02021646499633789s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007979869842529297s
Believability | Calculation of trust value for Cell Cycle Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cco took 2.602499485015869s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.26421546936035156s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025391578674316406s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cdao took 2.6050479412078857s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.1961669921875e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.00035762786865234375s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2669224739074707s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02042388916015625s
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.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008602142333984375s
Believability | Calculation of trust value for Chemical entities of biological interest took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-chebi took 2.5319535732269287s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.2438507080078125e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.26123619079589844s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002522468566894531s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.565866708755493s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 7.128715515136719e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.24678277969360352s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007510185241699219s
Believability | Calculation of trust value for Chemical Information Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cheminf took 2.5850000381469727s
Availability | SPARQL endpoint availability check for Cell type took 4.220008850097656e-05s
Availability | VoID file availability check for Cell type took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Cell type took 0.23747658729553223s
Reputation | Calculation of the PageRank for Cell type took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003952980041503906s
Believability | Calculation of trust value for Cell type took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-cl took 2.536015748977661s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.27428627014160156s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.02026057243347168s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0007901191711425781s
Believability | Calculation of trust value for Cell Line Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-clo took 2.6602323055267334s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.24786877632141113s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020947933197021484s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001952648162841797s
Believability | Calculation of trust value for Clinical Measurement Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cmo took 2.539644718170166s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.250683069229126s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002052783966064453s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cno took 2.639619827270508s
Availability | SPARQL endpoint availability check for Wheat trait took 4.220008850097656e-05s
Availability | VoID file availability check for Wheat trait took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.2571382522583008s
Reputation | Calculation of the PageRank for Wheat trait took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for Wheat trait took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.1021575927734375e-05s
Believability | Calculation of trust value for Wheat trait took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.651796817779541s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.982948303222656e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.26282382011413574s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020229101181030273s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00034308433532714844s
Believability | Calculation of trust value for Cognitive Atlas took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cogat took 2.615633010864258s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 5.841255187988281e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.3506591320037842s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007772445678710938s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cogpo took 2.6204044818878174s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.315376281738281e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.27019214630126953s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00042438507080078125s
Believability | Calculation of trust value for Current Procedural Terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cpt took 2.675995111465454s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.315376281738281e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3128194808959961s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017323493957519531s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-csp took 3.002861261367798s
Availability | SPARQL endpoint availability check for COSTART took 8.630752563476562e-05s
Availability | VoID file availability check for COSTART took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for COSTART took 0.27828550338745117s
Reputation | Calculation of the PageRank for COSTART took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009739398956298828s
Believability | Calculation of trust value for COSTART took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-cst took 2.6352264881134033s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.38690185546875e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.2665591239929199s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020139217376708984s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.00048470497131347656s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ctcae took 2.6242847442626953s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 5.125999450683594e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.28184080123901367s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00046706199645996094s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ctx took 2.635246515274048s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.410743713378906e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2656514644622803s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00029158592224121094s
Believability | Calculation of trust value for Dendritic cell took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.61985182762146s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.839897155761719e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.25815606117248535s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.58306884765625e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ddanat took 2.569913148880005s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.27077698707580566s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020580530166625977s
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.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009357929229736328s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ddi took 2.7347562313079834s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.25913405418395996s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.225440979003906e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.5922727584838867s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.24199151992797852s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020394086837768555s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00018215179443359375s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.613786220550537s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.839897155761719e-05s
Availability | VoID file availability check for Human disease ontology took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.24386262893676758s
Reputation | Calculation of the PageRank for Human disease ontology took 0.02015519142150879s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006508827209472656s
Believability | Calculation of trust value for Human disease ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-doid took 2.546165943145752s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2827277183532715s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007848739624023438s
Believability | Calculation of trust value for Electrocardiography Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ecg took 2.5918970108032227s
Availability | SPARQL endpoint availability check for Evidence codes took 4.2438507080078125e-05s
Availability | VoID file availability check for Evidence codes took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2576618194580078s
Reputation | Calculation of the PageRank for Evidence codes took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for Evidence codes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 2.9802322387695312e-05s
Believability | Calculation of trust value for Evidence codes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-eco took 2.6466336250305176s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.29346275329589844s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017044544219970703s
Believability | Calculation of trust value for Experimental Factor Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-efo took 3.0039925575256348s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.38690185546875e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2800116539001465s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011582374572753906s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 1.52587890625e-05s
INFO | --- Analysis for bioportal-ehda took 2.599973440170288s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.1961669921875e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.27491164207458496s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007216930389404297s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.6238911151885986s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.458427429199219e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.26719093322753906s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005283355712890625s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.672757863998413s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.220008850097656e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2948598861694336s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.021619558334350586s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0011975765228271484s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.7670135498046875e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-emap took 2.6056699752807617s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Environment Ontology took 0.001706838607788086s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.28191256523132324s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0003974437713623047s
Believability | Calculation of trust value for Environment Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-envo took 2.644221544265747s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 5.507469177246094e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2823624610900879s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020266056060791016s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00029730796813964844s
Believability | Calculation of trust value for Plant environmental conditions took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-eo took 2.618408203125s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.25855064392089844s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.001180887222290039s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ep took 2.6337380409240723s
Availability | SPARQL endpoint availability check for Epilepsy took 4.267692565917969e-05s
Availability | VoID file availability check for Epilepsy took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.283139705657959s
Reputation | Calculation of the PageRank for Epilepsy took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00014352798461914062s
Believability | Calculation of trust value for Epilepsy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-epileponto took 2.6731748580932617s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.315376281738281e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2561671733856201s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011696815490722656s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ero took 2.659795045852661s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.6253204345703125e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.25544095039367676s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020371198654174805s
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.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011296272277832031s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ev took 2.5642807483673096s
Availability | SPARQL endpoint availability check for ExO took 4.291534423828125e-05s
Availability | VoID file availability check for ExO took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for ExO took 0.25771331787109375s
Reputation | Calculation of the PageRank for ExO took 0.020677804946899414s
Interlinking | Calculation of Degree of Connection for ExO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0002493858337402344s
Believability | Calculation of trust value for ExO took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-exo took 2.6863324642181396s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.25783205032348633s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.022513389587402344s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.0001125335693359375s
Believability | Calculation of trust value for Fungal gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fao took 2.490812301635742s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.1961669921875e-05s
Availability | VoID file availability check for Biological imaging methods took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.29822421073913574s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020296812057495117s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.0001900196075439453s
Believability | Calculation of trust value for Biological imaging methods took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fbbi took 2.7250661849975586s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2693920135498047s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006382465362548828s
Believability | Calculation of trust value for Drosophila gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbbt took 2.5801713466644287s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.38690185546875e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.27533888816833496s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00042438507080078125s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbcv took 2.6602437496185303s
Availability | SPARQL endpoint availability check for Drosophila development took 4.315376281738281e-05s
Availability | VoID file availability check for Drosophila development took 0.0003571510314941406s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2834446430206299s
Reputation | Calculation of the PageRank for Drosophila development took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.291534423828125e-05s
Believability | Calculation of trust value for Drosophila development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbdv took 2.5263588428497314s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2838308811187744s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020284652709960938s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003619194030761719s
Believability | Calculation of trust value for Fly taxonomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fbsp took 2.7352304458618164s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.1484832763671875e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2913360595703125s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0012273788452148438s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002865791320800781s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.5964925289154053s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2794504165649414s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020182371139526367s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004000663757324219s
Believability | Calculation of trust value for Family Health History Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fhho took 2.6445746421813965s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0011966228485107422s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.29290103912353516s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010404586791992188s
Believability | Calculation of trust value for Influenza Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-flu took 2.6061441898345947s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 5.340576171875e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2534000873565674s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.079673767089844e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fma took 2.6055963039398193s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2669517993927002s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020277023315429688s
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.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00012540817260742188s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fypo took 2.6075308322906494s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 7.009506225585938e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.27465295791625977s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020996809005737305s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.940696716308594e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-geospecies took 2.627734422683716s
Availability | SPARQL endpoint availability check for General Formal Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2627742290496826s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00015974044799804688s
Believability | Calculation of trust value for General Formal Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gfo took 2.6565942764282227s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.291534423828125e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.28449130058288574s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.02017378807067871s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005986690521240234s
Believability | Calculation of trust value for General Formal Ontology: Biology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.7076284885406494s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.506111145019531e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2445058822631836s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0009214878082275391s
Believability | Calculation of trust value for Gene Ontology Extension took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.5876190662384033s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Gene Ontology took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.24730968475341797s
Reputation | Calculation of the PageRank for Gene Ontology took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008554458618164062s
Believability | Calculation of trust value for Gene Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.6258883476257324s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.124641418457031e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.2704174518585205s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.24249267578125e-05s
Believability | Calculation of trust value for Cereal Plant Development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-gro took 2.648993968963623s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.286313533782959s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00043320655822753906s
Believability | Calculation of trust value for Cereal plant gross anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.672840118408203s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 0.0005395412445068359s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.27348780632019043s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.021519899368286133s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007500648498535156s
Believability | Calculation of trust value for Gene Regulation Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.592604160308838s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.27734804153442383s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005571842193603516s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-hao took 2.608308792114258s
Availability | SPARQL endpoint availability check for HCPCS took 4.649162292480469e-05s
Availability | VoID file availability check for HCPCS took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for HCPCS took 0.28405141830444336s
Reputation | Calculation of the PageRank for HCPCS took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.000225067138671875s
Believability | Calculation of trust value for HCPCS took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.719482421875s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.6253204345703125e-05s
Availability | VoID file availability check for Health Level Seven took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.28007030487060547s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0013039112091064453s
Believability | Calculation of trust value for Health Level Seven took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hl7 took 2.679943561553955s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 0.0005972385406494141s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2698860168457031s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003364086151123047s
Believability | Calculation of trust value for HEALTH_INDICATORS took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.6742630004882812s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2731590270996094s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.0279159545898438e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hom took 2.6665120124816895s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 5.364418029785156e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.26062893867492676s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.0517578125e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.565457582473755s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.3452329635620117s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006260871887207031s
Believability | Calculation of trust value for Human Phenotype Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.718094825744629s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.26721954345703125s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010290145874023438s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hpio took 2.6450695991516113s
Availability | SPARQL endpoint availability check for HUGO took 4.267692565917969e-05s
Availability | VoID file availability check for HUGO took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for HUGO took 0.2595202922821045s
Reputation | Calculation of the PageRank for HUGO took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for HUGO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.392333984375e-05s
Believability | Calculation of trust value for HUGO took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hugo took 2.5358967781066895s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.24689388275146484s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006620883941650391s
Believability | Calculation of trust value for Information Artifact Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-iao took 2.556610107421875s
Availability | SPARQL endpoint availability check for ICD10 took 4.124641418457031e-05s
Availability | VoID file availability check for ICD10 took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for ICD10 took 0.3691697120666504s
Reputation | Calculation of the PageRank for ICD10 took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008413791656494141s
Believability | Calculation of trust value for ICD10 took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd10 took 2.8458333015441895s
Availability | SPARQL endpoint availability check for ICD10CM took 4.2438507080078125e-05s
Availability | VoID file availability check for ICD10CM took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.27572083473205566s
Reputation | Calculation of the PageRank for ICD10CM took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006034374237060547s
Believability | Calculation of trust value for ICD10CM took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.6753339767456055s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.38690185546875e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.27770161628723145s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00017881393432617188s
Believability | Calculation of trust value for ICD-10-PCS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.6221559047698975s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.24501752853393555s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006587505340576172s
Believability | Calculation of trust value for International Classification of Diseases took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.610764265060425s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.267692565917969e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.28423428535461426s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020589590072631836s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.00044417381286621094s
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.6312313079833984s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.1961669921875e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.25235533714294434s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.00122833251953125s
Believability | Calculation of trust value for International Classification for Nursing Practice took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icnp took 2.6614537239074707s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.696846008300781e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.26459169387817383s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00046706199645996094s
Believability | Calculation of trust value for International Classification of Primary Care took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icpc took 2.6488218307495117s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 8.654594421386719e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.280184268951416s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0009176731109619141s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.5793471336364746s
Availability | SPARQL endpoint availability check for ICPS Network took 7.319450378417969e-05s
Availability | VoID file availability check for ICPS Network took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2567315101623535s
Reputation | Calculation of the PageRank for ICPS Network took 0.020101070404052734s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002162456512451172s
Believability | Calculation of trust value for ICPS Network took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icps took 2.67981219291687s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 5.745887756347656e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.26056456565856934s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008566379547119141s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ido took 2.6423792839050293s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.28408312797546387s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011551380157470703s
Believability | Calculation of trust value for Brucellosis Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-idobru took 2.672783136367798s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.266634464263916s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013036727905273438s
Believability | Calculation of trust value for Malaria Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-idomal took 2.666720151901245s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.315376281738281e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2647056579589844s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003211498260498047s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-iev took 2.6011369228363037s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.2438507080078125e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.25827908515930176s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.0001544952392578125s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-imgt took 2.6068837642669678s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.267692565917969e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2749767303466797s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020145654678344727s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005030632019042969s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-imr took 2.5908384323120117s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2621932029724121s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020597219467163086s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007994174957275391s
Believability | Calculation of trust value for Interaction Network Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ino took 2.6586875915527344s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 5.507469177246094e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0008740425109863281s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2500178813934326s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.170967102050781e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.5400638580322266s
Availability | SPARQL endpoint availability check for IxnO took 4.1961669921875e-05s
Availability | VoID file availability check for IxnO took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for IxnO took 0.26580190658569336s
Reputation | Calculation of the PageRank for IxnO took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for IxnO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018835067749023438s
Believability | Calculation of trust value for IxnO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ixno took 2.6464247703552246s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.649162292480469e-05s
Availability | VoID file availability check for SysMO-JERM took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2749347686767578s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.02043771743774414s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003802776336669922s
Believability | Calculation of trust value for SysMO-JERM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-jerm took 2.649916410446167s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2826721668243408s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020284414291381836s
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.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-kisao took 2.685516595840454s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.220008850097656e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2815430164337158s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0001952648162841797s
Believability | Calculation of trust value for Loggerhead nesting took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-lhn took 2.5619661808013916s
Availability | SPARQL endpoint availability check for Lipid Ontology took 5.125999450683594e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.2594642639160156s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.0203092098236084s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020813941955566406s
Believability | Calculation of trust value for Lipid Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lipro took 2.5102577209472656s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 7.104873657226562e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3200051784515381s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018148422241210938s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-lnc took 3.0538644790649414s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2711794376373291s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0007073879241943359s
Believability | Calculation of trust value for Mouse adult gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ma took 2.6521658897399902s
Availability | SPARQL endpoint availability check for Multiple alignment took 5.340576171875e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.28366947174072266s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0009105205535888672s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002448558807373047s
Believability | Calculation of trust value for Multiple alignment took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mao took 2.529984712600708s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.315376281738281e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.28085780143737793s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020218372344970703s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006735324859619141s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mat took 2.678767681121826s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.1961669921875e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.25844860076904297s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00042891502380371094s
Believability | Calculation of trust value for Breast tissue cell lines took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.619513750076294s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.25305628776550293s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007491111755371094s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl took 2.5912296772003174s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cell line ontology took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2504706382751465s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0013895034790039062s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.583439350128174s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.220008850097656e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.284712553024292s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00027871131896972656s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mcv took 2.6916017532348633s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.220008850097656e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.29074788093566895s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02011275291442871s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00016498565673828125s
Believability | Calculation of trust value for Master Drug Data Base took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mddb took 2.697763204574585s
Availability | SPARQL endpoint availability check for MedDRA took 5.0067901611328125e-05s
Availability | VoID file availability check for MedDRA took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2650938034057617s
Reputation | Calculation of the PageRank for MedDRA took 0.020149707794189453s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0009620189666748047s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0012280941009521484s
Believability | Calculation of trust value for MedDRA took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mdr took 2.6136858463287354s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.220008850097656e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2839479446411133s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008716583251953125s
Believability | Calculation of trust value for MedlinePlus Health Topics took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.6105856895446777s
Availability | SPARQL endpoint availability check for MeGO took 4.1961669921875e-05s
Availability | VoID file availability check for MeGO took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for MeGO took 0.2576327323913574s
Reputation | Calculation of the PageRank for MeGO took 0.020175695419311523s
Interlinking | Calculation of Degree of Connection for MeGO took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014662742614746094s
Believability | Calculation of trust value for MeGO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mego took 2.5820159912109375s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.1961669921875e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.31940460205078125s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02049994468688965s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0017642974853515625s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.1192948818206787s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.250762939453125s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006077289581298828s
Believability | Calculation of trust value for Mental Functioning Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mf took 2.5521152019500732s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.267692565917969e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.3069648742675781s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020199060440063477s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005397796630859375s
Believability | Calculation of trust value for Medaka fish anatomy and development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mfo took 2.594715118408203s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.27205324172973633s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020921707153320312s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0010402202606201172s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0009031295776367188s
Believability | Calculation of trust value for Emotion Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mfoem took 2.7401065826416016s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.26963186264038086s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010919570922851562s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mhc took 2.570544958114624s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.2438507080078125e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2568936347961426s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.02019643783569336s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006697177886962891s
Believability | Calculation of trust value for Protein-protein interaction took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mi took 2.5239362716674805s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.172325134277344e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2439723014831543s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020210981369018555s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007255077362060547s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-miro took 2.5282421112060547s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.26583194732666016s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020258188247680664s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001404285430908203s
Believability | Calculation of trust value for Measurement Method Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mmo took 2.5520358085632324s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.23126506805419922s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003864765167236328s
Believability | Calculation of trust value for MGED Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mo took 2.506894111633301s
Availability | SPARQL endpoint availability check for Protein modification took 4.2438507080078125e-05s
Availability | VoID file availability check for Protein modification took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2620890140533447s
Reputation | Calculation of the PageRank for Protein modification took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Protein modification took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00023651123046875s
Believability | Calculation of trust value for Protein modification took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mod took 2.658337116241455s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.124641418457031e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.2650027275085449s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020119905471801758s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006308555603027344s
Believability | Calculation of trust value for Mammalian phenotype took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mp took 2.65358567237854s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.220008850097656e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.27477383613586426s
Reputation | Calculation of the PageRank for Mouse pathology took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0010001659393310547s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0005910396575927734s
Believability | Calculation of trust value for Mouse pathology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mpath took 2.6286768913269043s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.291534423828125e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2703588008880615s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003573894500732422s
Believability | Calculation of trust value for Mass spectrometry took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ms took 2.683331251144409s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.220008850097656e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3219282627105713s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020307302474975586s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018477439880371094s
Believability | Calculation of trust value for Medical Subject Headings took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-msh took 3.053109645843506s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.2438507080078125e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2653489112854004s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02029132843017578s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00016450881958007812s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-mthch took 2.667180299758911s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.2604701519012451s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020098447799682617s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007863044738769531s
Believability | Calculation of trust value for Natural Products Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-natpro took 2.6154184341430664s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.1961669921875e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.27176642417907715s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020797252655029297s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0007913112640380859s
Believability | Calculation of trust value for NCBI organismal classification took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.656343936920166s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 5.91278076171875e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3047659397125244s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0020020008087158203s
Believability | Calculation of trust value for NCI Thesaurus took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ncit took 3.014202833175659s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.267692565917969e-05s
Availability | VoID file availability check for National Drug Data File took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.25527429580688477s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02055811882019043s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006284713745117188s
Believability | Calculation of trust value for National Drug Data File took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nddf took 2.5912909507751465s
Availability | SPARQL endpoint availability check for National Drug File took 4.363059997558594e-05s
Availability | VoID file availability check for National Drug File took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for National Drug File took 0.25504231452941895s
Reputation | Calculation of the PageRank for National Drug File took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012035369873046875s
Believability | Calculation of trust value for National Drug File took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.594331979751587s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.57763671875e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2725520133972168s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011789798736572266s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.633331060409546s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.27926111221313477s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0009317398071289062s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0007314682006835938s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-neomark took 2.647798538208008s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.2669100761413574s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012063980102539062s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.6649439334869385s
Availability | SPARQL endpoint availability check for NIFSTD took 4.2438507080078125e-05s
Availability | VoID file availability check for NIFSTD took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3184947967529297s
Reputation | Calculation of the PageRank for NIFSTD took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019485950469970703s
Believability | Calculation of trust value for NIFSTD took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-nif took 3.1133289337158203s
Availability | SPARQL endpoint availability check for NIF Cell took 4.267692565917969e-05s
Availability | VoID file availability check for NIF Cell took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.24702215194702148s
Reputation | Calculation of the PageRank for NIF Cell took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013251304626464844s
Believability | Calculation of trust value for NIF Cell took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.54003643989563s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.6253204345703125e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.2597692012786865s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014040470123291016s
Believability | Calculation of trust value for NIF Dysfunction took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.553842782974243s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.27620911598205566s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005893707275390625s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nigo took 2.619135856628418s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 0.00012755393981933594s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2834911346435547s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005741119384765625s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nmr took 2.645320415496826s
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.0004792213439941406s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.23986387252807617s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011992454528808594s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.5484414100646973s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.2498488426208496s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011870861053466797s
Believability | Calculation of trust value for NanoParticle Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-npo took 2.5741569995880127s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.25846147537231445s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007512569427490234s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-oae took 2.5611722469329834s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 5.984306335449219e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.25969362258911133s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0015697479248046875s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-obi took 2.574416399002075s
Availability | SPARQL endpoint availability check for OBOE took 4.410743713378906e-05s
Availability | VoID file availability check for OBOE took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for OBOE took 0.26937365531921387s
Reputation | Calculation of the PageRank for OBOE took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for OBOE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011873245239257812s
Believability | Calculation of trust value for OBOE took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-oboe took 2.5250794887542725s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.458427429199219e-05s
Availability | VoID file availability check for OBOE SBC took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2537069320678711s
Reputation | Calculation of the PageRank for OBOE SBC took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008494853973388672s
Believability | Calculation of trust value for OBOE SBC took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.4975879192352295s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 5.602836608886719e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.26436352729797363s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020964384078979492s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005850791931152344s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ocre took 2.556072473526001s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 5.173683166503906e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2672398090362549s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0009264945983886719s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-odgi took 2.608299970626831s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 7.271766662597656e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2710583209991455s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008976459503173828s
Believability | Calculation of trust value for Ontology for Genetic Interval took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ogi took 2.5826854705810547s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.315376281738281e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.24680399894714355s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002994537353515625s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ogmd took 2.6513078212738037s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.4345855712890625e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.27016615867614746s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020522594451904297s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006823539733886719s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ogms took 2.651923656463623s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.6253204345703125e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.24641799926757812s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.02077507972717285s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011293888092041016s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-omim took 2.6211352348327637s
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.0004775524139404297s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.2660214900970459s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003769397735595703s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-omit took 2.580693483352661s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 7.843971252441406e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.297926664352417s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006580352783203125s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-omrse took 2.4190196990966797s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2655467987060547s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02064800262451172s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.000774383544921875s
Believability | Calculation of trust value for Ontology of Data Mining took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ontodm took 2.6273319721221924s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.27197957038879395s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020594120025634766s
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.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002434253692626953s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ontodt took 2.6666247844696045s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.57763671875e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.278048038482666s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006108283996582031s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.6519663333892822s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2739279270172119s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009405612945556641s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-opl took 2.6313960552215576s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.291534423828125e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2665834426879883s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0009112358093261719s
Believability | Calculation of trust value for Phenotypic quality took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pato took 2.555534839630127s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.57763671875e-05s
Availability | VoID file availability check for Physician Data Query took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2617063522338867s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008637905120849609s
Believability | Calculation of trust value for Physician Data Query took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pdq took 2.644749879837036s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.1961669921875e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.26581478118896484s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020181655883789062s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007793903350830078s
Believability | Calculation of trust value for Pediatric Terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pedterm took 2.6383795738220215s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.00039386749267578125s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2557494640350342s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020273447036743164s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019288063049316406s
Believability | Calculation of trust value for Parasite Experiment Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-peo took 2.6616835594177246s
Availability | SPARQL endpoint availability check for PHARE took 4.267692565917969e-05s
Availability | VoID file availability check for PHARE took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for PHARE took 0.2612133026123047s
Reputation | Calculation of the PageRank for PHARE took 0.020212173461914062s
Interlinking | Calculation of Degree of Connection for PHARE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006256103515625s
Believability | Calculation of trust value for PHARE took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-phare took 2.586667776107788s
Availability | SPARQL endpoint availability check for PKO_Re took 4.1961669921875e-05s
Availability | VoID file availability check for PKO_Re took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2854785919189453s
Reputation | Calculation of the PageRank for PKO_Re took 0.020432472229003906s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00018072128295898438s
Believability | Calculation of trust value for PKO_Re took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pko took 2.750913381576538s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.291534423828125e-05s
Availability | VoID file availability check for PMA 2010 took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2566821575164795s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020206212997436523s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008778572082519531s
Believability | Calculation of trust value for PMA 2010 took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-pma took 2.6426949501037598s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.220008850097656e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.26423144340515137s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.02030467987060547s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001666545867919922s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pmr took 2.6290595531463623s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Plant Anatomy took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.27419400215148926s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020862102508544922s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00039505958557128906s
Believability | Calculation of trust value for Plant Anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-po took 2.694579839706421s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.267692565917969e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2716522216796875s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020097017288208008s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.461143493652344e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.6057796478271484s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Plant Ontology took 0.00048828125s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.24185395240783691s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020249366760253906s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004291534423828125s
Believability | Calculation of trust value for Plant Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.6538918018341064s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.1961669921875e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.27654314041137695s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020038843154907227s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006487369537353516s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pr took 2.636606454849243s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.2438507080078125e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2563905715942383s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00024962425231933594s
Believability | Calculation of trust value for Proteomics data and process provenance took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-propreo took 2.677800416946411s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Pathway ontology took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.29558658599853516s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012135505676269531s
Believability | Calculation of trust value for Pathway ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pw took 2.643608808517456s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.2660996913909912s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-qibo took 2.6301865577697754s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.315376281738281e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3248720169067383s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 4.100799560546875e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.001735687255859375s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rcd took 3.0176827907562256s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.26551318168640137s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.0001220703125s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rctontology took 2.5908029079437256s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2746100425720215s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.012222290039062e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-repo took 2.5549919605255127s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.220008850097656e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2618105411529541s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00018715858459472656s
Believability | Calculation of trust value for Physico-chemical process took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rex took 2.4958581924438477s
Availability | SPARQL endpoint availability check for RadLex took 4.172325134277344e-05s
Availability | VoID file availability check for RadLex took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for RadLex took 0.25311756134033203s
Reputation | Calculation of the PageRank for RadLex took 0.021027326583862305s
Interlinking | Calculation of Degree of Connection for RadLex took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0016202926635742188s
Believability | Calculation of trust value for RadLex took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rid took 2.544637441635132s
Availability | SPARQL endpoint availability check for RNA ontology took 4.1961669921875e-05s
Availability | VoID file availability check for RNA ontology took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2595796585083008s
Reputation | Calculation of the PageRank for RNA ontology took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for RNA ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005555152893066406s
Believability | Calculation of trust value for RNA ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rnao took 2.5563035011291504s
Availability | SPARQL endpoint availability check for Role Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Role Ontology took 0.00041031837463378906s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.23656868934631348s
Reputation | Calculation of the PageRank for Role Ontology took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for Role Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Role Ontology took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018286705017089844s
Believability | Calculation of trust value for Role Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-roleo took 2.581874370574951s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 5.698204040527344e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.2919802665710449s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001747608184814453s
Believability | Calculation of trust value for Rat Strain Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rs took 2.6019608974456787s
Availability | SPARQL endpoint availability check for RxNORM took 4.363059997558594e-05s
Availability | VoID file availability check for RxNORM took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2558743953704834s
Reputation | Calculation of the PageRank for RxNORM took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0009813308715820312s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006992816925048828s
Believability | Calculation of trust value for RxNORM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.611448049545288s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.267692565917969e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0011255741119384766s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.25427818298339844s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.001024007797241211s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sao took 2.6143012046813965s
Availability | SPARQL endpoint availability check for Systems Biology took 4.3392181396484375e-05s
Availability | VoID file availability check for Systems Biology took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.24695062637329102s
Reputation | Calculation of the PageRank for Systems Biology took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004642009735107422s
Believability | Calculation of trust value for Systems Biology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sbo took 2.6100165843963623s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.887580871582031e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.26096081733703613s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010275840759277344s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sbro took 2.6217868328094482s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.28134751319885254s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020273208618164062s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 3.4332275390625e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013267993927001953s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sdo took 2.6203460693359375s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.4345855712890625e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.25765132904052734s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003361701965332031s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sep took 2.690948724746704s
Availability | SPARQL endpoint availability check for Student Health Record took 4.1961669921875e-05s
Availability | VoID file availability check for Student Health Record took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2535433769226074s
Reputation | Calculation of the PageRank for Student Health Record took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for Student Health Record took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004343986511230469s
Believability | Calculation of trust value for Student Health Record took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-shr took 2.6010351181030273s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2584707736968994s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012350082397460938s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sio took 3.5672550201416016s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.291534423828125e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2785453796386719s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0001957416534423828s
Believability | Calculation of trust value for Situation-Based Access Control took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-sitbac took 2.6019771099090576s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.267692565917969e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3248867988586426s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.001924276351928711s
Believability | Calculation of trust value for SNOMED Clinical Terms took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-snomedct took 3.066714286804199s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.2598307132720947s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006732940673828125s
Believability | Calculation of trust value for SNP-Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-snpo took 2.547855854034424s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.4345855712890625e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2617909908294678s
Reputation | Calculation of the PageRank for Sequence types and features took 0.02110886573791504s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0008757114410400391s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0006670951843261719s
Believability | Calculation of trust value for Sequence types and features took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.535468101501465s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.1961669921875e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.33834075927734375s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020791292190551758s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015628337860107422s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sopharm took 3.1771771907806396s
Availability | SPARQL endpoint availability check for SoyOntology took 4.172325134277344e-05s
Availability | VoID file availability check for SoyOntology took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.28451085090637207s
Reputation | Calculation of the PageRank for SoyOntology took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012731552124023438s
Believability | Calculation of trust value for SoyOntology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-soy took 2.6249470710754395s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.27865123748779297s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00030803680419921875s
Believability | Calculation of trust value for Spider Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-spd took 2.544398784637451s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2728691101074219s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0003046989440917969s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 1.5020370483398438e-05s
INFO | --- Analysis for bioportal-spto took 2.657095432281494s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 5.3882598876953125e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.2601501941680908s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004394054412841797s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sso took 2.6248884201049805s
Availability | SPARQL endpoint availability check for Software Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Software Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.24651026725769043s
Reputation | Calculation of the PageRank for Software Ontology took 0.020248889923095703s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004208087921142578s
Believability | Calculation of trust value for Software Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-swo took 2.618138313293457s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2775120735168457s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.021121978759765625s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002300739288330078s
Believability | Calculation of trust value for Tick gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tads took 2.622225761413574s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.26080870628356934s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008845329284667969s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tao took 2.8046162128448486s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 5.340576171875e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2571451663970947s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.606910705566406e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-taxrank took 2.574847459793091s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.1484832763671875e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.26056766510009766s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 6.842613220214844e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-teddy took 2.6886637210845947s
Availability | SPARQL endpoint availability check for Time Event Ontology took 0.0006260871887207031s
Availability | VoID file availability check for Time Event Ontology took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2739424705505371s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020173072814941406s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008134841918945312s
Believability | Calculation of trust value for Time Event Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-teo took 2.609221935272217s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.1484832763671875e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2717099189758301s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0004107952117919922s
Believability | Calculation of trust value for Mosquito gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-tgma took 2.6290793418884277s
Availability | SPARQL endpoint availability check for thesaurus took 5.14984130859375e-05s
Availability | VoID file availability check for thesaurus took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for thesaurus took 0.24678444862365723s
Reputation | Calculation of the PageRank for thesaurus took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.556510925292969e-05s
Believability | Calculation of trust value for thesaurus took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.542876958847046s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.291534423828125e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.27677249908447266s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00034546852111816406s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.6289174556732178s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 0.0005583763122558594s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2572975158691406s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.02112412452697754s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008115768432617188s
Believability | Calculation of trust value for Translational Medicine Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tmo took 2.6177663803100586s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.28252339363098145s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.000152587890625s
Believability | Calculation of trust value for Plant Trait Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-to took 2.635941982269287s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.9114227294921875e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.28122401237487793s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020116567611694336s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00017499923706054688s
Believability | Calculation of trust value for TOK_Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tok took 2.7893006801605225s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.315376281738281e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.2862722873687744s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020168542861938477s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0002009868621826172s
Believability | Calculation of trust value for Teleost taxonomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-tto took 2.6493146419525146s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.57763671875e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2662382125854492s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020174741744995117s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010232925415039062s
Believability | Calculation of trust value for Uber anatomy ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-uberon took 2.5999410152435303s
Availability | SPARQL endpoint availability check for Units Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Units Ontology took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.24714899063110352s
Reputation | Calculation of the PageRank for Units Ontology took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00022125244140625s
Believability | Calculation of trust value for Units Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.637613296508789s
Availability | SPARQL endpoint availability check for Units of measurement took 5.245208740234375e-05s
Availability | VoID file availability check for Units of measurement took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.23787951469421387s
Reputation | Calculation of the PageRank for Units of measurement took 0.020444393157958984s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002880096435546875s
Believability | Calculation of trust value for Units of measurement took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-uo took 2.640333414077759s
Availability | SPARQL endpoint availability check for VANDF took 4.363059997558594e-05s
Availability | VoID file availability check for VANDF took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for VANDF took 0.270587682723999s
Reputation | Calculation of the PageRank for VANDF took 0.020270824432373047s
Interlinking | Calculation of Degree of Connection for VANDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VANDF took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007169246673583984s
Believability | Calculation of trust value for VANDF took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-vandf took 2.6543736457824707s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2631528377532959s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020244121551513672s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004146099090576172s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-vao took 2.597766637802124s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.1961669921875e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.25529956817626953s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006041526794433594s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vhog took 2.597947359085083s
Availability | SPARQL endpoint availability check for VIVO took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for VIVO took 0.26090574264526367s
Reputation | Calculation of the PageRank for VIVO took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for VIVO took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00036334991455078125s
Believability | Calculation of trust value for VIVO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-vivo took 2.6918067932128906s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.2708909511566162s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020303964614868164s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012295246124267578s
Believability | Calculation of trust value for Vaccine Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vo took 2.680189371109009s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2775747776031494s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.02015209197998047s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020170211791992188s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-vt took 2.6814987659454346s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2562892436981201s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0009262561798095703s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005743503570556641s
Believability | Calculation of trust value for C. elegans gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-wbbt took 2.572924852371216s
Availability | SPARQL endpoint availability check for C. elegans development took 4.5299530029296875e-05s
Availability | VoID file availability check for C. elegans development took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2748067378997803s
Reputation | Calculation of the PageRank for C. elegans development took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.124641418457031e-05s
Believability | Calculation of trust value for C. elegans development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-wbls took 2.6265673637390137s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.172325134277344e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.26128363609313965s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.606910705566406e-05s
Believability | Calculation of trust value for C. elegans phenotype took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.5665924549102783s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 5.030632019042969e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2702360153198242s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005931854248046875s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-who took 2.5939879417419434s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.1484832763671875e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.27637743949890137s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006859302520751953s
Believability | Calculation of trust value for Xenopus anatomy and development took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-xao took 2.6379568576812744s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.26456642150878906s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002295970916748047s
Believability | Calculation of trust value for Experimental Conditions Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-xco took 2.661146879196167s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.172325134277344e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.2487194538116455s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002627372741699219s
Believability | Calculation of trust value for Yeast phenotypes took 2.9802322387695312e-05s
INFO | --- Analysis for bioportal-ypo took 2.6130518913269043s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 0.0005314350128173828s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2795727252960205s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007960796356201172s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-zfa took 2.6737756729125977s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.410743713378906e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.2899150848388672s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.02027153968811035s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 6.67572021484375e-06s
INFO | --- Analysis for Bioportal_link took 4.055182218551636s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4597320556640625s
Availability | VoID file availability check for BioSamples RDF took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2594139575958252s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 4.839897155761719e-05s
Believability | Calculation of trust value for BioSamples RDF took 7.3909759521484375e-06s
INFO | --- Analysis for biosamples-rdf took 3.527308940887451s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.9564352035522461s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0003571510314941406s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2561454772949219s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011396408081054688s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for bis-linked-data took 3.3068177700042725s
Availability | SPARQL endpoint availability check for Bitzi took 3.9577484130859375e-05s
Availability | VoID file availability check for Bitzi took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for Bitzi took 0.25631141662597656s
Reputation | Calculation of the PageRank for Bitzi took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for Bitzi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Bitzi took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bitzi took 6.4373016357421875e-06s
INFO | --- Analysis for bitzi took 2.846693515777588s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.0531158447265625e-05s
Availability | VoID file availability check for BizkaiSense took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.2494065761566162s
Reputation | Calculation of the PageRank for BizkaiSense took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.1948089599609375e-05s
Believability | Calculation of trust value for BizkaiSense took 6.9141387939453125e-06s
INFO | --- Analysis for bizkaisense took 2.8692739009857178s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.38690185546875e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.270068883895874s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020235538482666016s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.8848648071289062e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.867813110351562e-06s
INFO | --- Analysis for blabla-itemlist took 2.8655831813812256s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.076957702636719e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2698550224304199s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0009350776672363281s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.147125244140625e-05s
Believability | Calculation of trust value for blabla.itemlist took 6.9141387939453125e-06s
INFO | --- Analysis for blabla_itemlist took 2.9200708866119385s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.410743713378906e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.24781394004821777s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.00543212890625e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for bll-thesaurus took 3.6072306632995605s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.342275857925415s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.24320220947265625s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 7.605552673339844e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.4543533325195312e-05s
INFO | --- Analysis for bluk-bnb took 13.390887022018433s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.2588624954223633s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006918907165527344s
Extra | Recovery of all triples for Thesaurus BNCF took 72.82511758804321s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5372519493103027s
Amount of data | Number of triples check for Thesaurus BNCF took 1.2618632316589355s
Interoperability | New terms check for Thesaurus BNCF took 1.545240879058838s
Versatility | Languages check for Thesaurus BNCF took 12.596484899520874s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 1.7009062767028809s
Security | Check HTTPS for Thesaurus BNCF took 0.07670736312866211s
Interpretability | RDF structures check for Thesaurus BNCF took 0.1028285026550293s
Versatility | Serialization formats check for Thesaurus BNCF took 0.11760854721069336s
Availability | RDF dump link check for Thesaurus BNCF took 0.10952281951904297s
License | MR license check for Thesaurus BNCF took 0.11144042015075684s
License | HR license check for Thesaurus BNCF took 0.3032517433166504s
Amount of data | Number of property check for Thesaurus BNCF took 0.11631107330322266s
Understandability | Number of label check for Thesaurus BNCF took 0.36161017417907715s
Understandability | URI regex check for Thesaurus BNCF took 0.22484922409057617s
Understandability | Vocabs check for Thesaurus BNCF took 0.11110806465148926s
Verifiability | Authors check for Thesaurus BNCF took 0.11471295356750488s
Verifiability | Publishers check for Thesaurus BNCF took 0.10436248779296875s
Performance | Throughput check for Thesaurus BNCF took 10.7277250289917s
Amount of data | Check the number of entities for Thesaurus BNCF took 6.771087646484375e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.10674929618835449s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.11146092414855957s
Interlinking | skos check for Thesaurus BNCF took 0.22774553298950195s
Interlinking | skos check for Thesaurus BNCF took 0.1974189281463623s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.1060786247253418s
Currency | Creation date check for Thesaurus BNCF took 0.2480933666229248s
Currency | Modification date check for Thesaurus BNCF took 0.22729229927062988s
Rep.Conc. | URIs length for Thesaurus BNCF took 27.634623050689697s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.10645341873168945s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.10779833793640137s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.11126446723937988s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 14.471687078475952s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5062668323516846s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.912862777709961s
Consistency | Disjoint class check for Thesaurus BNCF took 0.10993742942810059s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.4190714359283447s
Consistency | Misplaced classes for Thesaurus BNCF took 7.041365385055542s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 10.246183395385742s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.5755176544189453s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.949954032897949s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4636120796203613s
Security | Sign check for Thesaurus BNCF took 0.13476085662841797s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 22.171997547149658s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3774862289428711s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.019950389862060547s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 6.747245788574219e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.430511474609375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 6.67572021484375e-06s
INFO | --- Analysis for bncf-ns took 236.02075576782227s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4894537925720215s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006275177001953125s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.436081886291504s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.55788254737854s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.2479419708251953s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.186269998550415s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.32383394241333s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.124891757965088s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6053011417388916s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.49092769622802734s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.46665358543395996s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4217829704284668s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.536750078201294s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.288257122039795s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.915137529373169s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7464859485626221s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6608824729919434s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.41948604583740234s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38923120498657227s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33023571968078613s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.987503290176392s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.699562072753906e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33765482902526855s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0228314399719238s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3601102828979492s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.30005311965942383s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3846120834350586s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7323033809661865s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5527153015136719s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 17.77072262763977s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2968144416809082s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2939722537994385s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3716468811035156s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7559916973114014s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02420330047607422s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.029141664505004883s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35503625869750977s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.456839323043823s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3892817497253418s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.458475112915039s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8747515678405762s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.82227110862732s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03224372863769531s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.343780755996704s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3372921943664551s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9852657318115234s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.81784987449646s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.020886898040771484s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.106231689453125e-06s
INFO | --- Analysis for bpr took 467.2111802101135s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.4345855712890625e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.25728821754455566s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.961822509765625e-05s
Believability | Calculation of trust value for Brazilian Politicians took 5.0067901611328125e-06s
INFO | --- Analysis for brazilian-politicians took 3.0664865970611572s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.076957702636719e-05s
Availability | VoID file availability check for BrazilianCities took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.2726895809173584s
Reputation | Calculation of the PageRank for BrazilianCities took 0.021292448043823242s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0009124279022216797s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.2901763916015625e-05s
Believability | Calculation of trust value for BrazilianCities took 8.106231689453125e-06s
INFO | --- Analysis for braziliancities took 3.4246370792388916s
Availability | SPARQL endpoint availability check for Bricklink took 1.5537190437316895s
Availability | VoID file availability check for Bricklink took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Bricklink took 0.27464771270751953s
Reputation | Calculation of the PageRank for Bricklink took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.580352783203125e-05s
Believability | Calculation of trust value for Bricklink took 6.9141387939453125e-06s
INFO | --- Analysis for bricklink took 10.020451545715332s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.172951459884644s
Availability | VoID file availability check for British Museum Collection took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2608652114868164s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.552436828613281e-05s
Believability | Calculation of trust value for British Museum Collection took 6.67572021484375e-06s
INFO | --- Analysis for british-museum-collection took 72.62783122062683s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.1484832763671875e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.26822996139526367s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.9577484130859375e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 6.4373016357421875e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.4634389877319336s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.076957702636719e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.27876853942871094s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 3.337860107421875e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 7.62939453125e-06s
INFO | --- Analysis for bsv took 3.3503530025482178s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3184633255004883s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.26077866554260254s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02070450782775879s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.7881393432617188e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.67572021484375e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 5.330678939819336s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.363059997558594e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.26601195335388184s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.24249267578125e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 7.867813110351562e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.8852949142456055s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.076957702636719e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.2723114490509033s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 2.9087066650390625e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 7.152557373046875e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.8686585426330566s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.27509140968322754s
Availability | VoID file availability check for business.data.gov.uk took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2608006000518799s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 6.723403930664062e-05s
Believability | Calculation of trust value for business.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for business-data-gov-uk took 2.848196268081665s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 1.0331006050109863s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.27648043632507324s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 4.3392181396484375e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 7.62939453125e-06s
INFO | --- Analysis for BVMC took 7.444443464279175s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.0531158447265625e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.29183483123779297s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.0208585262298584s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 2.956390380859375e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 6.198883056640625e-06s
INFO | --- Analysis for cabbage took 2.8871617317199707s
Availability | SPARQL endpoint availability check for cablegate took 1.695563793182373s
Availability | VoID file availability check for cablegate took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for cablegate took 0.28052282333374023s
Reputation | Calculation of the PageRank for cablegate took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for cablegate took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.009506225585938e-05s
Believability | Calculation of trust value for cablegate took 5.7220458984375e-06s
INFO | --- Analysis for cablegate took 16.51544952392578s
Availability | SPARQL endpoint availability check for Calames took 4.315376281738281e-05s
Availability | VoID file availability check for Calames took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Calames took 0.27694010734558105s
Reputation | Calculation of the PageRank for Calames took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for Calames took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Calames took 3.4809112548828125e-05s
Believability | Calculation of trust value for Calames took 5.9604644775390625e-06s
INFO | --- Analysis for calames took 4.3578667640686035s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.42917346954345703s
Availability | VoID file availability check for CaLiGraph took 0.0002319812774658203s
Extra | Recovery of all triples for CaLiGraph took 1.8453714847564697s
Performance | Total latancy measurement for CaLiGraph took 1.1847167015075684s
Amount of data | Number of triples check for CaLiGraph took 12.532292604446411s
Interoperability | New terms check for CaLiGraph took 1.9782493114471436s
Versatility | Languages check for CaLiGraph took 60.319342613220215s
Interpretability | Number of blank nodes check for CaLiGraph took 0.32288336753845215s
Security | Check HTTPS for CaLiGraph took 0.15200328826904297s
Interpretability | RDF structures check for CaLiGraph took 0.36313772201538086s
Versatility | Serialization formats check for CaLiGraph took 0.35646843910217285s
Availability | RDF dump link check for CaLiGraph took 0.26111483573913574s
License | MR license check for CaLiGraph took 0.34580159187316895s
License | HR license check for CaLiGraph took 60.32030153274536s
Amount of data | Number of property check for CaLiGraph took 0.2883625030517578s
Understandability | Number of label check for CaLiGraph took 3.3723032474517822s
Understandability | URI regex check for CaLiGraph took 0.554335355758667s
Understandability | Vocabs check for CaLiGraph took 0.30452704429626465s
Verifiability | Authors check for CaLiGraph took 0.3233182430267334s
Verifiability | Publishers check for CaLiGraph took 0.25608396530151367s
Performance | Throughput check for CaLiGraph took 11.710054159164429s
Amount of data | Check the number of entities for CaLiGraph took 0.014554023742675781s
Verifiability | Contribs. check for CaLiGraph took 0.3641226291656494s
Interlinking | sameAs chians check for CaLiGraph took 0.7632660865783691s
Interlinking | skos check for CaLiGraph took 0.4886503219604492s
Interlinking | skos check for CaLiGraph took 0.28659987449645996s
Timeliness | dataset update frequency check for CaLiGraph took 0.42211413383483887s
Currency | Creation date check for CaLiGraph took 0.5989792346954346s
Currency | Modification date check for CaLiGraph took 0.615999698638916s
Rep.Conc. | URIs length for CaLiGraph took 61.16407299041748s
Interoperability | New vocabularies check for CaLiGraph took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.29106616973876953s
Accuracy | Check Functional Property for CaLiGraph took 0.3428785800933838s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.30617785453796387s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5850589275360107s
Accuracy | Check White space in annotation for CaLiGraph took 0.026547908782958984s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05126309394836426s
Consistency | Disjoint class check for CaLiGraph took 0.2832784652709961s
Consistency | Check Misplaced properties for CaLiGraph took 61.130592346191406s
Consistency | Misplaced classes for CaLiGraph took 0.5067832469940186s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9199166297912598s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2860918045043945s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.56753063201904s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03350424766540527s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.49375343322753906s
Security | Sign check for CaLiGraph took 0.44681692123413086s
Availability | Check URIs Dereferenciability for CaLiGraph took 13.212010860443115s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.7971503734588623s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.790855407714844e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 8.106231689453125e-06s
INFO | --- Analysis for CaLiGraph took 1669.0756154060364s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2794795036315918s
Availability | VoID file availability check for CaLiGraph took 0.000804901123046875s
Extra | Recovery of all triples for CaLiGraph took 1.1552300453186035s
Performance | Total latancy measurement for CaLiGraph took 1.255504846572876s
Amount of data | Number of triples check for CaLiGraph took 12.604228496551514s
Interoperability | New terms check for CaLiGraph took 2.1196320056915283s
Versatility | Languages check for CaLiGraph took 60.37791872024536s
Interpretability | Number of blank nodes check for CaLiGraph took 20.39646863937378s
Security | Check HTTPS for CaLiGraph took 0.15840697288513184s
Interpretability | RDF structures check for CaLiGraph took 21.656675815582275s
Versatility | Serialization formats check for CaLiGraph took 25.674211263656616s
Availability | RDF dump link check for CaLiGraph took 15.772164344787598s
License | MR license check for CaLiGraph took 0.5585930347442627s
License | HR license check for CaLiGraph took 60.32356548309326s
Amount of data | Number of property check for CaLiGraph took 17.690011262893677s
Understandability | Number of label check for CaLiGraph took 27.57383394241333s
Understandability | URI regex check for CaLiGraph took 20.33853507041931s
Understandability | Vocabs check for CaLiGraph took 2.41198992729187s
Verifiability | Authors check for CaLiGraph took 0.26264524459838867s
Verifiability | Publishers check for CaLiGraph took 0.2856161594390869s
Performance | Throughput check for CaLiGraph took 50.35306739807129s
Amount of data | Check the number of entities for CaLiGraph took 0.021328449249267578s
Verifiability | Contribs. check for CaLiGraph took 10.437346458435059s
Interlinking | sameAs chians check for CaLiGraph took 16.8301842212677s
Interlinking | skos check for CaLiGraph took 5.974529981613159s
Interlinking | skos check for CaLiGraph took 14.576325416564941s
Timeliness | dataset update frequency check for CaLiGraph took 29.963258743286133s
Currency | Creation date check for CaLiGraph took 12.741757869720459s
Currency | Modification date check for CaLiGraph took 15.390408515930176s
Rep.Conc. | URIs length for CaLiGraph took 61.04966497421265s
Interoperability | New vocabularies check for CaLiGraph took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2645714282989502s
Accuracy | Check Functional Property for CaLiGraph took 0.3494250774383545s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.27605342864990234s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6281476020812988s
Accuracy | Check White space in annotation for CaLiGraph took 0.02639317512512207s
Accuracy | Check Datatype consistency for CaLiGraph took 0.052077293395996094s
Consistency | Disjoint class check for CaLiGraph took 0.25837159156799316s
Consistency | Check Misplaced properties for CaLiGraph took 60.92745542526245s
Consistency | Misplaced classes for CaLiGraph took 0.5661942958831787s
Consistency | Check Ontology hijacking for CaLiGraph took 2.0472517013549805s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3369102478027344s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.66268062591553s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.036067962646484375s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4994544982910156s
Security | Sign check for CaLiGraph took 0.2677321434020996s
Availability | Check URIs Dereferenciability for CaLiGraph took 11.598987340927124s
Completeness | Calculation of interlinking completeness for CaLiGraph took 1.3178579807281494s
Reputation | Calculation of the PageRank for CaLiGraph took 0.0209805965423584s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 7.152557373046875e-06s
INFO | --- Analysis for caligraph took 1905.1780257225037s
Availability | SPARQL endpoint availability check for can-link took 4.124641418457031e-05s
Availability | VoID file availability check for can-link took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for can-link took 0.2572197914123535s
Reputation | Calculation of the PageRank for can-link took 0.02006077766418457s
Interlinking | Calculation of Degree of Connection for can-link took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for can-link took 2.8371810913085938e-05s
Believability | Calculation of trust value for can-link took 1.1444091796875e-05s
INFO | --- Analysis for can-link took 4.5838706493377686s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.05991220474243164s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.6969592571258545s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.02106499671936035s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0008287429809570312s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.24249267578125e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 8.344650268554688e-06s
INFO | --- Analysis for cap-italy-rdf took 3.4113166332244873s
Availability | SPARQL endpoint availability check for person took 4.601478576660156e-05s
Availability | VoID file availability check for person took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for person took 0.2543506622314453s
Reputation | Calculation of the PageRank for person took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for person took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for person took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for person took 3.123283386230469e-05s
Believability | Calculation of trust value for person took 7.62939453125e-06s
INFO | --- Analysis for card took 3.262342691421509s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.410743713378906e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2685542106628418s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 5.364418029785156e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 8.106231689453125e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.37739896774292s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.220008850097656e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.27950477600097656s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.0040740966796875e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 7.3909759521484375e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 3.4482581615448s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.5592834949493408s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0002970695495605469s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 90.31281781196594s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9625720977783203s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 8.494677782058716s
Interoperability | New terms check for Norway catch records dataset @PSNC took 13.785076379776001s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.1934311389923s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 3.1171181201934814s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.2606539726257324s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 8.944092988967896s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.2507317066192627s
License | MR license check for Norway catch records dataset @PSNC took 0.35321950912475586s
License | HR license check for Norway catch records dataset @PSNC took 300.17771315574646s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.2728300094604492s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.417992353439331s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.7704880237579346s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.40945005416870117s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.1858508586883545s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.2723572254180908s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.531978845596313s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.295608520507812e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.17969107627868652s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.19690895080566406s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.44809746742248535s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4468514919281006s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 3.930025577545166s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.5139455795288086s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.22686004638671875s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 146.509183883667s
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.1991109848022461s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.32711315155029297s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.26866912841796875s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 34.34110355377197s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6814088821411133s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.7054800987243652s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.20597338676452637s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 84.9760684967041s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.473012685775757s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 32.56000280380249s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.4038245677947998s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 82.40963172912598s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.750047206878662s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5491471290588379s
Security | Sign check for Norway catch records dataset @PSNC took 0.7679414749145508s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 10.39827013015747s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.45522093772888184s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.021874189376831055s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 3.552436828613281e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2211.5753650665283s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.4345855712890625e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.25364232063293457s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010275840759277344s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 8.106231689453125e-06s
INFO | --- Analysis for ce4r took 19.70756721496582s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.8952231407165527s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.00041937828063964844s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.118577003479004s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 1.1939122676849365s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3722512722015381s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6519742012023926s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.12688970565796s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21648764610290527s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22478985786437988s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14775967597961426s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.29911375045776367s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22575116157531738s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2977290153503418s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1617581844329834s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.32607579231262207s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3392002582550049s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1606302261352539s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2614147663116455s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2571723461151123s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.710541009902954s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.534027099609375e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26100754737854004s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1535930633544922s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.652458667755127s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1382596492767334s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22856569290161133s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5577707290649414s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.559424877166748s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.18156099319458s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1289515495300293s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2421579360961914s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.3663496971130371s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.5756521224975586s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028325319290161133s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.027834177017211914s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.35553526878356934s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.3481593132019043s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.0005276203155518s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.9765501022338867s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5640718936920166s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03033757209777832s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.3969275951385498s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.13663959503173828s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2400.7577652931213s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.6489622592926025s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.02296733856201172s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 5.0067901611328125e-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 7.152557373046875e-06s
INFO | --- Analysis for ceo took 2526.7441346645355s
Availability | SPARQL endpoint availability check for Charging Stations took 4.291534423828125e-05s
Availability | VoID file availability check for Charging Stations took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.25602269172668457s
Reputation | Calculation of the PageRank for Charging Stations took 0.020219087600708008s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.0279159545898438e-05s
Believability | Calculation of trust value for Charging Stations took 7.867813110351562e-06s
INFO | --- Analysis for charging-stations took 4.6657469272613525s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.267692565917969e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0007998943328857422s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.26988887786865234s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.1948089599609375e-05s
Believability | Calculation of trust value for Chat Game corpus took 6.9141387939453125e-06s
INFO | --- Analysis for chat-game-corpus took 13.826068639755249s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.1484832763671875e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.26429009437561035s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.266334533691406e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 7.152557373046875e-06s
INFO | --- Analysis for chebi took 2.890843391418457s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.172325134277344e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.28945183753967285s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.936622619628906e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 7.62939453125e-06s
INFO | --- Analysis for chem2bio2rdf took 135.22170114517212s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.6250905990600586s
Availability | VoID file availability check for ChEMBL RDF took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.2854902744293213s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.0067901611328125e-05s
Believability | Calculation of trust value for ChEMBL RDF took 7.62939453125e-06s
INFO | --- Analysis for chembl-rdf took 3.8446521759033203s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.5749666690826416s
Availability | VoID file availability check for chemdb  dataset took 0.0002658367156982422s
Extra | Recovery of all triples for chemdb  dataset took 5.018213987350464s
Performance | Total latancy measurement for chemdb  dataset took 2.530989646911621s
Amount of data | Number of triples check for chemdb  dataset took 0.5515718460083008s
Interoperability | New terms check for chemdb  dataset took 9.589317560195923s
Versatility | Languages check for chemdb  dataset took 27.861470222473145s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5262749195098877s
Interpretability | RDF structures check for chemdb  dataset took 0.5611720085144043s
Versatility | Serialization formats check for chemdb  dataset took 1.3677771091461182s
Availability | RDF dump link check for chemdb  dataset took 0.7812023162841797s
License | MR license check for chemdb  dataset took 2.6248085498809814s
License | HR license check for chemdb  dataset took 3.9703242778778076s
Amount of data | Number of property check for chemdb  dataset took 0.531829833984375s
Understandability | Number of label check for chemdb  dataset took 4.642031192779541s
Understandability | URI regex check for chemdb  dataset took 1.710162878036499s
Understandability | Vocabs check for chemdb  dataset took 0.7652640342712402s
Verifiability | Authors check for chemdb  dataset took 1.060978651046753s
Verifiability | Publishers check for chemdb  dataset took 0.7940258979797363s
Performance | Throughput check for chemdb  dataset took 12.557445764541626s
Amount of data | Check the number of entities for chemdb  dataset took 6.866455078125e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.7685205936431885s
Interlinking | sameAs chians check for chemdb  dataset took 1.0875225067138672s
Interlinking | skos check for chemdb  dataset took 2.074774742126465s
Interlinking | skos check for chemdb  dataset took 0.4954960346221924s
Timeliness | dataset update frequency check for chemdb  dataset took 0.9280438423156738s
Currency | Creation date check for chemdb  dataset took 1.3282196521759033s
Currency | Modification date check for chemdb  dataset took 1.030205249786377s
Rep.Conc. | URIs length for chemdb  dataset took 11.484827756881714s
Interoperability | New vocabularies check for chemdb  dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5197029113769531s
Accuracy | Check Functional Property for chemdb  dataset took 0.7640969753265381s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.7479162216186523s
Accuracy | Check Empty annotation labels for chemdb  dataset took 10.192410707473755s
Accuracy | Check White space in annotation for chemdb  dataset took 0.03022909164428711s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03353452682495117s
Consistency | Disjoint class check for chemdb  dataset took 0.7957186698913574s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2145130634307861s
Consistency | Misplaced classes for chemdb  dataset took 0.6101584434509277s
Consistency | Check Ontology hijacking for chemdb  dataset took 5.1767659187316895s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.2965800762176514s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.9995558261871338s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.032265663146972656s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5281305313110352s
Security | Sign check for chemdb  dataset took 1.8110990524291992s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2699.8332023620605s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.956352710723877s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021289587020874023s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 8.153915405273438e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb  dataset took 6.9141387939453125e-06s
INFO | --- Analysis for chemdb-basicInfo took 3775.103055715561s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5301713943481445s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.00027441978454589844s
Extra | Recovery of all triples for chemdb estimated properties dataset took 35.00089454650879s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.516348361968994s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5556621551513672s
Interoperability | New terms check for chemdb estimated properties dataset took 5.946354627609253s
Versatility | Languages check for chemdb estimated properties dataset took 29.24444341659546s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.519603967666626s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5304374694824219s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.499408483505249s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.8385214805603027s
License | MR license check for chemdb estimated properties dataset took 2.738070011138916s
License | HR license check for chemdb estimated properties dataset took 4.017378330230713s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5305488109588623s
Understandability | Number of label check for chemdb estimated properties dataset took 4.834195613861084s
Understandability | URI regex check for chemdb estimated properties dataset took 1.9079978466033936s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.8179240226745605s
Verifiability | Authors check for chemdb estimated properties dataset took 1.1390001773834229s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.8268954753875732s
Performance | Throughput check for chemdb estimated properties dataset took 13.45047378540039s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 6.008148193359375e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.8184926509857178s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.162947416305542s
Interlinking | skos check for chemdb estimated properties dataset took 2.100637197494507s
Interlinking | skos check for chemdb estimated properties dataset took 0.4968903064727783s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.0980682373046875s
Currency | Creation date check for chemdb estimated properties dataset took 1.3098249435424805s
Currency | Modification date check for chemdb estimated properties dataset took 1.017470121383667s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 9.255526781082153s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.4973337650299072s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.8078751564025879s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7944753170013428s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 5.916072607040405s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.030813217163085938s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.033354759216308594s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.8661787509918213s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2230918407440186s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.5977282524108887s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 11.607954740524292s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.2754528522491455s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9711124897003174s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03229665756225586s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5214059352874756s
Security | Sign check for chemdb estimated properties dataset took 2.072803258895874s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2702.8940222263336s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.5899097919464111s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.021253585815429688s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.3113021850585938e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 3798.634054660797s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5264551639556885s
Availability | VoID file availability check for chemdb phase transition dataset took 0.00029397010803222656s
Extra | Recovery of all triples for chemdb phase transition dataset took 32.256985902786255s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.540487051010132s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5370385646820068s
Interoperability | New terms check for chemdb phase transition dataset took 6.087291240692139s
Versatility | Languages check for chemdb phase transition dataset took 28.11917519569397s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5349798202514648s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5357279777526855s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.5775370597839355s
Availability | RDF dump link check for chemdb phase transition dataset took 0.8675079345703125s
License | MR license check for chemdb phase transition dataset took 2.883103847503662s
License | HR license check for chemdb phase transition dataset took 4.051240682601929s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5222244262695312s
Understandability | Number of label check for chemdb phase transition dataset took 6.066587924957275s
Understandability | URI regex check for chemdb phase transition dataset took 2.0560944080352783s
Understandability | Vocabs check for chemdb phase transition dataset took 0.8351764678955078s
Verifiability | Authors check for chemdb phase transition dataset took 1.1736998558044434s
Verifiability | Publishers check for chemdb phase transition dataset took 0.7387247085571289s
Performance | Throughput check for chemdb phase transition dataset took 12.495847463607788s
Amount of data | Check the number of entities for chemdb phase transition dataset took 3.075599670410156e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.886035680770874s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.238368272781372s
Interlinking | skos check for chemdb phase transition dataset took 2.2439708709716797s
Interlinking | skos check for chemdb phase transition dataset took 0.49927687644958496s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.285949945449829s
Currency | Creation date check for chemdb phase transition dataset took 1.4028432369232178s
Currency | Modification date check for chemdb phase transition dataset took 1.030879259109497s
Rep.Conc. | URIs length for chemdb phase transition dataset took 9.588085651397705s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.5043129920959473s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.8372490406036377s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.8341662883758545s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 9.985251903533936s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.03039264678955078s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03303194046020508s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.8348197937011719s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2450613975524902s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6096704006195068s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 5.174643039703369s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.2986512184143066s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.009420156478882s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03241157531738281s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5261340141296387s
Security | Sign check for chemdb phase transition dataset took 2.2256553173065186s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2692.3670575618744s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.9320037364959717s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021192312240600586s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 7.3909759521484375e-06s
INFO | --- Analysis for chemdb-phaseTransition took 3777.0165004730225s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.517096757888794s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0002803802490234375s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 28.75696349143982s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.5197486877441406s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5521078109741211s
Interoperability | New terms check for chemdb thermochemistry dataset took 4.425829172134399s
Versatility | Languages check for chemdb thermochemistry dataset took 28.951773405075073s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5185770988464355s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.515960693359375s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.482144832611084s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.8390004634857178s
License | MR license check for chemdb thermochemistry dataset took 2.9813332557678223s
License | HR license check for chemdb thermochemistry dataset took 4.066629886627197s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.528883695602417s
Understandability | Number of label check for chemdb thermochemistry dataset took 5.049841642379761s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.8764793872833252s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.8341372013092041s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.1937475204467773s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.8275525569915771s
Performance | Throughput check for chemdb thermochemistry dataset took 13.951392650604248s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 5.4836273193359375e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.8189201354980469s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.1387920379638672s
Interlinking | skos check for chemdb thermochemistry dataset took 2.025693893432617s
Interlinking | skos check for chemdb thermochemistry dataset took 0.4906890392303467s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.1198580265045166s
Currency | Creation date check for chemdb thermochemistry dataset took 1.337109088897705s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0107436180114746s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 9.827719449996948s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.5029263496398926s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.7992472648620605s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.7765605449676514s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 5.839213609695435s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.0307619571685791s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03347039222717285s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.8383955955505371s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2126517295837402s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6161153316497803s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 7.569707632064819s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.276822566986084s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.978440523147583s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03206586837768555s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5250973701477051s
Security | Sign check for chemdb thermochemistry dataset took 2.1196091175079346s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2695.811842441559s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.971839189529419s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.021116018295288086s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.937980651855469e-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 7.62939453125e-06s
INFO | --- Analysis for chemdb-thermochemistry took 3773.7983667850494s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 7.653236389160156e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.2688908576965332s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.123283386230469e-05s
Believability | Calculation of trust value for ChemPedia RDF took 7.152557373046875e-06s
INFO | --- Analysis for chempedia-rdf took 11.846143245697021s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.3392181396484375e-05s
Availability | VoID file availability check for Chiman Maru took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.26410889625549316s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.0040740966796875e-05s
Believability | Calculation of trust value for Chiman Maru took 7.152557373046875e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 3.7349436283111572s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.6873505115509s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0003509521484375s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.2552628517150879s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.0212404727935791s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.910064697265625e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 7.152557373046875e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 800.1939451694489s
Availability | SPARQL endpoint availability check for Chronicling America took 4.2438507080078125e-05s
Availability | VoID file availability check for Chronicling America took 0.00029969215393066406s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.2611417770385742s
Reputation | Calculation of the PageRank for Chronicling America took 0.020605087280273438s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.0001010894775390625s
Believability | Calculation of trust value for Chronicling America took 6.4373016357421875e-06s
INFO | --- Analysis for chronicling-america took 7.156599283218384s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.7918121814727783s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0004999637603759766s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 84.38950610160828s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.5190033912658691s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6280443668365479s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.090947389602661s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.390268325805664s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.576953649520874s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3253517150878906s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3465409278869629s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 9.877963066101074s
License | MR license check for Cultural Heritage Thesaurus took 0.31052708625793457s
License | HR license check for Cultural Heritage Thesaurus took 0.4125235080718994s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.2993631362915039s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.34211230278015137s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5768537521362305s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.2935295104980469s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.33796024322509766s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.27170872688293457s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.324959754943848s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.987022399902344e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.3149585723876953s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.30561304092407227s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.282698392868042s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.30974507331848145s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.30486369132995605s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5708408355712891s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6289794445037842s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 9.616332054138184s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 4.652480125427246s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.27442502975463867s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.31012701988220215s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.3020155429840088s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 3.3636531829833984s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22653889656066895s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.28077268600463867s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.0073258876800537s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2950568199157715s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 5.65400767326355s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.0209009647369385s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001499652862548828s
Security | Sign check for Cultural Heritage Thesaurus took 0.2831552028656006s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 284.09307980537415s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.4886307716369629s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.09380030632019043s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00010275840759277344s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 5.568156719207764s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 8.821487426757812e-06s
INFO | --- Analysis for cht took 465.9561004638672s
Availability | SPARQL endpoint availability check for ciard-ring took 4.649162292480469e-05s
Availability | VoID file availability check for ciard-ring took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.29412102699279785s
Reputation | Calculation of the PageRank for ciard-ring took 0.04416060447692871s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.7206878662109375e-05s
Believability | Calculation of trust value for ciard-ring took 7.3909759521484375e-06s
INFO | --- Analysis for ciard-ring took 5.12290620803833s
Availability | SPARQL endpoint availability check for Cine Figure took 4.172325134277344e-05s
Availability | VoID file availability check for Cine Figure took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.2545626163482666s
Reputation | Calculation of the PageRank for Cine Figure took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.315376281738281e-05s
Believability | Calculation of trust value for Cine Figure took 6.9141387939453125e-06s
INFO | --- Analysis for Cine_Figure took 2.806691884994507s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 1.3440656661987305s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.28005504608154297s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.0209503173828125s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.3392181396484375e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 5.497476816177368s
Availability | SPARQL endpoint availability check for CIPFA took 5.53131103515625e-05s
Availability | VoID file availability check for CIPFA took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for CIPFA took 0.2659034729003906s
Reputation | Calculation of the PageRank for CIPFA took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for CIPFA took 4.00543212890625e-05s
Believability | Calculation of trust value for CIPFA took 8.344650268554688e-06s
INFO | --- Analysis for cipfa took 2.675182819366455s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 0.2617619037628174s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.25042104721069336s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020654678344726562s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0008268356323242188s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00042128562927246094s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 7.152557373046875e-06s
INFO | --- Analysis for ckan took 3.772703170776367s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5144574642181396s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007393360137939453s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.25616908073425293s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 5.4836273193359375e-06s
INFO | --- Analysis for CLaSSES took 3.845695972442627s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.482269287109375e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2924840450286865s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.123283386230469e-05s
Believability | Calculation of trust value for Temples of the Classical World took 6.4373016357421875e-06s
INFO | --- Analysis for classical_temples took 3.888400077819824s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 12.693715572357178s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.24688124656677246s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.869171142578125e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 4.76837158203125e-06s
INFO | --- Analysis for clean-energy-data-reegle took 27.152029275894165s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.220008850097656e-05s
Availability | VoID file availability check for CLLD-afbo took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.24805259704589844s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.581710815429688e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.049041748046875e-05s
INFO | --- Analysis for clld-afbo took 3.7624447345733643s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.100799560546875e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.2557663917541504s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020534515380859375s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.796287536621094e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.0967254638671875e-05s
INFO | --- Analysis for clld-apics took 4.634440183639526s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.28325486183166504s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0008168220520019531s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.814697265625e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.049041748046875e-05s
INFO | --- Analysis for clld-ewave took 3.5291271209716797s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 8.678436279296875e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2637932300567627s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020271778106689453s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.679794311523438e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 7.152557373046875e-06s
INFO | --- Analysis for clld-glottolog took 3.922124147415161s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.2799973487854004s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.021227598190307617s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.82012939453125e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 6.9141387939453125e-06s
INFO | --- Analysis for clld-phoible took 4.572990894317627s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.24763107299804688s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.0108642578125e-05s
Believability | Calculation of trust value for CLLD-SAILS took 6.4373016357421875e-06s
INFO | --- Analysis for clld-sails took 3.612919330596924s
Availability | SPARQL endpoint availability check for CLLD-WALS took 6.794929504394531e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0003695487976074219s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.24851489067077637s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.058547973632812e-05s
Believability | Calculation of trust value for CLLD-WALS took 6.9141387939453125e-06s
INFO | --- Analysis for clld-wals took 3.9233016967773438s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.24740386009216309s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.0212099552154541s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0008013248443603516s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 8.368492126464844e-05s
Believability | Calculation of trust value for CLLD-WOLD took 7.152557373046875e-06s
INFO | --- Analysis for clld-wold took 3.4595835208892822s
Availability | SPARQL endpoint availability check for COD inventory took 4.124641418457031e-05s
Availability | VoID file availability check for COD inventory took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for COD inventory took 0.2597625255584717s
Reputation | Calculation of the PageRank for COD inventory took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for COD inventory took 2.9087066650390625e-05s
Believability | Calculation of trust value for COD inventory took 6.9141387939453125e-06s
INFO | --- Analysis for cod-inventory took 2.88533353805542s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.15292620658874512s
Availability | VoID file availability check for Cooperation Databank took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.28896570205688477s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 4.100799560546875e-05s
Believability | Calculation of trust value for Cooperation Databank took 6.9141387939453125e-06s
INFO | --- Analysis for CoDa took 2.5313920974731445s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.0531158447265625e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.2494337558746338s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 4.553794860839844e-05s
Believability | Calculation of trust value for CODE Endpoint took 6.9141387939453125e-06s
INFO | --- Analysis for code-endpoint took 2.9193968772888184s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.5666384696960449s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.28017592430114746s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.170967102050781e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 5.4836273193359375e-06s
INFO | --- Analysis for coins-openuplabs took 2.9849743843078613s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 2.965616226196289s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.26337146759033203s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 7.891654968261719e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 7.152557373046875e-06s
INFO | --- Analysis for CoLChina_sp2000 took 6.677603244781494s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.06971859931945801s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.26510000228881836s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.021490812301635742s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0011382102966308594s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.57763671875e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for colinda took 2.4960882663726807s
Availability | SPARQL endpoint availability check for CN  2012 took 28.319040298461914s
Availability | VoID file availability check for CN  2012 took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.7110378742218018s
Reputation | Calculation of the PageRank for CN  2012 took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.528594970703125e-05s
Believability | Calculation of trust value for CN  2012 took 5.0067901611328125e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 128.53790044784546s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.172325134277344e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.6999268531799316s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.075599670410156e-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 3.302678108215332s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.935264587402344e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.24053478240966797s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02166438102722168s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.4809112548828125e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 7.867813110351562e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.855672597885132s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 5.53131103515625e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.2665903568267822s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.021005630493164062s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.409385681152344e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 8.58306884765625e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.9703447818756104s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 5.078315734863281e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.2791464328765869s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.956390380859375e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 7.62939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.8589117527008057s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.100799560546875e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.2875807285308838s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.218650817871094e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 9.298324584960938e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.9826483726501465s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.40082740783691406s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.2797071933746338s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02201056480407715s
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.0010340213775634766s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 4.38690185546875e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for CompHistSem took 3.67557692527771s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.288165330886841s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0007123947143554688s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.254056453704834s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020303726196289062s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.314018249511719e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 6.9141387939453125e-06s
INFO | --- Analysis for comsode-d3-2 took 7.681333541870117s
Availability | SPARQL endpoint availability check for ConceptNet took 4.0531158447265625e-05s
Availability | VoID file availability check for ConceptNet took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.25604748725891113s
Reputation | Calculation of the PageRank for ConceptNet took 0.02065443992614746s
Interlinking | Calculation of Degree of Connection for ConceptNet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.0517578125e-05s
Believability | Calculation of trust value for ConceptNet took 1.2636184692382812e-05s
INFO | --- Analysis for conceptnet took 2.910475254058838s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.220008850097656e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.23957490921020508s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 9.226799011230469e-05s
Believability | Calculation of trust value for 2011 US Congress People took 4.5299530029296875e-06s
INFO | --- Analysis for congresspeople took 2.9279353618621826s
Availability | SPARQL endpoint availability check for MIMO took 0.24140596389770508s
Availability | VoID file availability check for MIMO took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for MIMO took 0.268247127532959s
Reputation | Calculation of the PageRank for MIMO took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for MIMO took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.1205673217773438e-05s
Believability | Calculation of trust value for MIMO took 7.62939453125e-06s
INFO | --- Analysis for CONNECTED took 3.541734457015991s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.124641418457031e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2508668899536133s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020166873931884766s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 2.6464462280273438e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.89149808883667s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.220008850097656e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.2713785171508789s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.956390380859375e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 6.67572021484375e-06s
INFO | --- Analysis for copac-library-catalogue took 2.8530068397521973s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.6253204345703125e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.2750060558319092s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.022602081298828125s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0010039806365966797s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 4.1484832763671875e-05s
Believability | Calculation of trust value for Copyright Free Music took 6.9141387939453125e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.6463301181793213s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.315376281738281e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.2531087398529053s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.021721601486206055s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.987022399902344e-05s
Believability | Calculation of trust value for CopyrightTermBank took 6.4373016357421875e-06s
INFO | --- Analysis for copyrighttermbank took 56.55916357040405s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.479585647583008s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0003540515899658203s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.30475687980651855s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.8623809814453125e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.1205673217773438e-05s
INFO | --- Analysis for core took 7.2838263511657715s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.6937227249145508s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002682209014892578s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 90.85360431671143s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 1.0129899978637695s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 8.380016565322876s
Interoperability | New terms check for Corine linked dataset @PSNC took 15.386154413223267s
Versatility | Languages check for Corine linked dataset @PSNC took 300.2457914352417s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 3.266275644302368s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.27579379081726074s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 10.855033159255981s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.3005976676940918s
License | MR license check for Corine linked dataset @PSNC took 0.6096405982971191s
License | HR license check for Corine linked dataset @PSNC took 300.1937458515167s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.2620563507080078s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.5382039546966553s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.6546580791473389s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.45238566398620605s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.20285344123840332s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.24363303184509277s
Performance | Throughput check for Corine linked dataset @PSNC took 11.55959701538086s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 8.344650268554688e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.19767093658447266s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.19797182083129883s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4410576820373535s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4354703426361084s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.413668632507324s
Currency | Creation date check for Corine linked dataset @PSNC took 0.46938633918762207s
Currency | Modification date check for Corine linked dataset @PSNC took 0.20355701446533203s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 151.88178420066833s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.18250393867492676s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.29644060134887695s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.3590068817138672s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 39.619380950927734s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.661999464035034s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.688201665878296s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.19605302810668945s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 82.0326144695282s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.330071449279785s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 30.601377725601196s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.3598320484161377s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 85.37361145019531s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.773416519165039s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.518418550491333s
Security | Sign check for Corine linked dataset @PSNC took 0.8092098236083984s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 11.168842315673828s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 1.4253060817718506s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 7.62939453125e-06s
INFO | --- Analysis for Corine_linked_dataset took 2227.3634564876556s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.410743713378906e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0003154277801513672s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.2737090587615967s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020784854888916016s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.147125244140625e-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.543285369873047s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.1484832763671875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2588818073272705s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 2.9802322387695312e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 6.9141387939453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 3.7563819885253906s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0005986690521240234s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.28971123695373535s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.8848648071289062e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 8.106231689453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.952451229095459s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.4345855712890625e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.25882863998413086s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.984306335449219e-05s
Believability | Calculation of trust value for Cornetto1.2 took 8.344650268554688e-06s
INFO | --- Analysis for cornetto took 13.50284719467163s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.7135288715362549s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.26360535621643066s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 4.6253204345703125e-05s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.1444091796875e-05s
INFO | --- Analysis for corporate-body took 3.7498555183410645s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.48780274391174316s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.26781320571899414s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 4.363059997558594e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for CorpusFibonacci took 3.8896842002868652s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.267692565917969e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.25263357162475586s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for corscheck took 2.9664485454559326s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.3869657516479492s
Availability | VoID file availability check for Country Name Authority List took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.24889707565307617s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.4836273193359375e-05s
Believability | Calculation of trust value for Country Name Authority List took 6.9141387939453125e-06s
INFO | --- Analysis for country-authority-list took 3.897536039352417s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.14369893074035645s
Availability | VoID file availability check for Courts thesaurus took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2679860591888428s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.723403930664062e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for courts-thesaurus took 2.479290246963501s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.6005957126617432s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.2746548652648926s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.724761962890625e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 7.152557373046875e-06s
INFO | --- Analysis for Covid-on-the-Web took 14.466205358505249s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.188364028930664s
Availability | VoID file availability check for CPA 2008 took 0.0009562969207763672s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.7242746353149414s
Reputation | Calculation of the PageRank for CPA 2008 took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.361701965332031e-05s
Believability | Calculation of trust value for CPA 2008 took 4.76837158203125e-06s
INFO | --- Analysis for cpa-2008 took 124.7868287563324s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.3332102298736572s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005877017974853516s
Extra | Recovery of all triples for Cooperative Patent Classification took 29.570099592208862s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.9443767070770264s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.17830467224121s
Versatility | Languages check for Cooperative Patent Classification took 120.07686805725098s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.20602202415466s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.1869792938232422s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.20040249824523926s
Availability | RDF dump link check for Cooperative Patent Classification took 0.15661025047302246s
License | MR license check for Cooperative Patent Classification took 0.1730194091796875s
License | HR license check for Cooperative Patent Classification took 90.24775195121765s
Amount of data | Number of property check for Cooperative Patent Classification took 0.19404363632202148s
Understandability | Number of label check for Cooperative Patent Classification took 90.16710758209229s
Understandability | URI regex check for Cooperative Patent Classification took 0.45800209045410156s
Understandability | Vocabs check for Cooperative Patent Classification took 0.20644450187683105s
Verifiability | Authors check for Cooperative Patent Classification took 0.2111961841583252s
Verifiability | Publishers check for Cooperative Patent Classification took 0.1943817138671875s
Performance | Throughput check for Cooperative Patent Classification took 10.736880540847778s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.724761962890625e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.18071579933166504s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.17612838745117188s
Interlinking | skos check for Cooperative Patent Classification took 0.21428847312927246s
Interlinking | skos check for Cooperative Patent Classification took 0.1896381378173828s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.1413891315460205s
Currency | Creation date check for Cooperative Patent Classification took 0.40317797660827637s
Currency | Modification date check for Cooperative Patent Classification took 0.39503979682922363s
Rep.Conc. | URIs length for Cooperative Patent Classification took 156.02346801757812s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.15702056884765625s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 17.633483409881592s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.968019723892212s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.8625288009643555s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.21775007247924805s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.27330422401428s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 20.82318091392517s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.6166114807128906s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.4618284702301s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.8188600540161133s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.2931833267211914s
Security | Sign check for Cooperative Patent Classification took 0.20444440841674805s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.473844289779663s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.6157901287078857s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 3.886222839355469e-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 1293.012915611267s
Availability | SPARQL endpoint availability check for CPC 2008 took 26.084531784057617s
Availability | VoID file availability check for CPC 2008 took 0.0008342266082763672s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.6836404800415039s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.552436828613281e-05s
Believability | Calculation of trust value for CPC 2008 took 5.7220458984375e-06s
INFO | --- Analysis for cpc-2008 took 128.28202629089355s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.54189109802246s
Availability | VoID file availability check for CPV  2003 took 0.0009171962738037109s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.7674386501312256s
Reputation | Calculation of the PageRank for CPV  2003 took 0.020644187927246094s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.910064697265625e-05s
Believability | Calculation of trust value for CPV  2003 took 4.5299530029296875e-06s
INFO | --- Analysis for cpv-2003 took 115.11456966400146s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.32920551300049s
Availability | VoID file availability check for CPV 2008 took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.2544095516204834s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020644426345825195s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.792213439941406e-05s
Believability | Calculation of trust value for CPV 2008 took 4.76837158203125e-06s
INFO | --- Analysis for cpv-2008 took 124.97057914733887s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.74480509757996s
Availability | VoID file availability check for crowdsourcing-fb took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.27660536766052246s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.6253204345703125e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 7.152557373046875e-06s
INFO | --- Analysis for crowdsourcing-fb took 536.1906111240387s
Availability | SPARQL endpoint availability check for CRTM took 4.57763671875e-05s
Availability | VoID file availability check for CRTM took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for CRTM took 0.2787330150604248s
Reputation | Calculation of the PageRank for CRTM took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.9087066650390625e-05s
Believability | Calculation of trust value for CRTM took 7.152557373046875e-06s
INFO | --- Analysis for crtm took 5.094614744186401s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.00543212890625e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.2693753242492676s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.0212099552154541s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.218650817871094e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 7.867813110351562e-06s
INFO | --- Analysis for crystal-eye took 3.359666347503662s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.653007984161377s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.2901120185852051s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.744529724121094e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 4.76837158203125e-06s
INFO | --- Analysis for ctic-public-dataset took 43.818095684051514s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.124641418457031e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.26160287857055664s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.0517578125e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 8.106231689453125e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 2.892312526702881s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.5601627826690674s
Availability | VoID file availability check for CulturaLinkedData took 0.0005474090576171875s
Extra | Recovery of all triples for CulturaLinkedData took 134.82815837860107s
Performance | Total latancy measurement for CulturaLinkedData took 4.5522260665893555s
Amount of data | Number of triples check for CulturaLinkedData took 5.002636194229126s
Interoperability | New terms check for CulturaLinkedData took 4.100982666015625s
Versatility | Languages check for CulturaLinkedData took 62.58535647392273s
Interpretability | Number of blank nodes check for CulturaLinkedData took 1.9067811965942383s
Interpretability | RDF structures check for CulturaLinkedData took 0.46622657775878906s
Versatility | Serialization formats check for CulturaLinkedData took 2.227205514907837s
Availability | RDF dump link check for CulturaLinkedData took 0.24271273612976074s
License | MR license check for CulturaLinkedData took 0.605553150177002s
License | HR license check for CulturaLinkedData took 62.44169497489929s
Amount of data | Number of property check for CulturaLinkedData took 0.18801474571228027s
Understandability | Number of label check for CulturaLinkedData took 1.226022720336914s
Understandability | URI regex check for CulturaLinkedData took 2.4551188945770264s
Understandability | Vocabs check for CulturaLinkedData took 2.0637171268463135s
Verifiability | Authors check for CulturaLinkedData took 2.1474320888519287s
Verifiability | Publishers check for CulturaLinkedData took 2.10599946975708s
Performance | Throughput check for CulturaLinkedData took 23.165277242660522s
Amount of data | Check the number of entities for CulturaLinkedData took 7.104873657226562e-05s
Verifiability | Contribs. check for CulturaLinkedData took 2.0677196979522705s
Interlinking | sameAs chians check for CulturaLinkedData took 0.38648486137390137s
Interlinking | skos check for CulturaLinkedData took 2.386103391647339s
Interlinking | skos check for CulturaLinkedData took 0.21059942245483398s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.3385007381439209s
Currency | Creation date check for CulturaLinkedData took 2.1500473022460938s
Currency | Modification date check for CulturaLinkedData took 2.138659715652466s
Rep.Conc. | URIs length for CulturaLinkedData took 67.44503164291382s
Interoperability | New vocabularies check for CulturaLinkedData took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.1667473316192627s
Accuracy | Check Functional Property for CulturaLinkedData took 2.044463634490967s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 1.9978079795837402s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 39.14964485168457s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6189184188842773s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.3243956565856934s
Consistency | Disjoint class check for CulturaLinkedData took 0.19506525993347168s
Consistency | Check Misplaced properties for CulturaLinkedData took 8.461126565933228s
Consistency | Misplaced classes for CulturaLinkedData took 4.221419811248779s
Consistency | Check Ontology hijacking for CulturaLinkedData took 42.759745597839355s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.346466302871704s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 9.642142534255981s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3806729316711426s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.16827178001403809s
Security | Sign check for CulturaLinkedData took 1.2697069644927979s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 11.743465900421143s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.828254222869873s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.02109384536743164s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.6716461181640625e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.6226043701171875e-06s
Believability | Calculation of trust value for CulturaLinkedData took 8.58306884765625e-06s
INFO | --- Analysis for culturalinkeddata took 644.1940710544586s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.1608126163482666s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0008530616760253906s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.26785945892333984s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.5299530029296875e-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 3.696859836578369s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.10088729858398438s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.25745248794555664s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02933979034423828s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0009570121765136719s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.933906555175781e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ares-rzp took 4.026772737503052s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11626791954040527s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.2532494068145752s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020174741744995117s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.266334533691406e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 5.0067901611328125e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 2.877521514892578s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.11172914505004883s
Availability | VoID file availability check for Integrated pollution registry took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.27553367614746094s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.6716461181640625e-05s
Believability | Calculation of trust value for Integrated pollution registry took 5.7220458984375e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.825982093811035s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10874652862548828s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.001444101333618164s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2816157341003418s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.022037982940673828s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0008497238159179688s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.62396240234375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 5.0067901611328125e-06s
INFO | --- Analysis for cz-contracts took 2.863130569458008s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.792213439941406e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0003247261047363281s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.24860882759094238s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0009765625s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.4332275390625e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-courts took 3.0565271377563477s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.10545539855957031s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2627999782562256s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.337860107421875e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-bans took 5.084550857543945s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.1083989143371582s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0008130073547363281s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.2504417896270752s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020032882690429688s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.218650817871094e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.666839599609375s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.12049174308776855s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.2644388675689697s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.504753112792969e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7609920501708984s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10736823081970215s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.28397226333618164s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020447731018066406s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 3.9577484130859375e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.8161158561706543s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.11629033088684082s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2672724723815918s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.218650817871094e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.7220458984375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.657800197601318s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 10.284111261367798s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.28972363471984863s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.021160602569580078s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.5762786865234375e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 4.5299530029296875e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 22.98619270324707s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 10.071650266647339s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2710742950439453s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020386457443237305s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.170967102050781e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 4.5299530029296875e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 22.797655820846558s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.9374406337738037s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.26262426376342773s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.62396240234375e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.8650968074798584s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3627495765686035s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.28203821182250977s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.2619903087615967s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3904287815093994s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.2815723419189453s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.504753112792969e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.471674680709839s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.4299337863922119s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.264493465423584s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.0202786922454834s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.504753112792969e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.3456506729125977s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.36559224128723145s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.28491640090942383s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.409385681152344e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.1767780780792236s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.4447922706604004s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2604539394378662s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02035355567932129s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.2901763916015625e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-regions took 3.024186372756958s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3946263790130615s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2669370174407959s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02436661720275879s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0011832714080810547s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.6253204345703125e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.2535107135772705s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.4119441509246826s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.25811767578125s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020230770111083984s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.62396240234375e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.2637827396392822s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.40733861923217773s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2476363182067871s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.743171691894531e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.289494276046753s
Availability | SPARQL endpoint availability check for ATC groups took 0.11635804176330566s
Availability | VoID file availability check for ATC groups took 0.00048828125s
Completeness | Calculation of interlinking completeness for ATC groups took 0.28301429748535156s
Reputation | Calculation of the PageRank for ATC groups took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.794929504394531e-05s
Believability | Calculation of trust value for ATC groups took 6.9141387939453125e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.7866005897521973s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10558152198791504s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.279843807220459s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020655393600463867s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.504753112792969e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.0067901611328125e-06s
INFO | --- Analysis for cz-fulfillments took 2.766937255859375s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.02987384796142578s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.26824402809143066s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.982948303222656e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 5.245208740234375e-06s
INFO | --- Analysis for cz-ic took 3.107215404510498s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.14094901084899902s
Availability | VoID file availability check for List of Czech data boxes took 0.0006532669067382812s
Extra | Recovery of all triples for List of Czech data boxes took 184.26409006118774s
Performance | Total latancy measurement for List of Czech data boxes took 0.5874981880187988s
Amount of data | Number of triples check for List of Czech data boxes took 18.138227939605713s
Interoperability | New terms check for List of Czech data boxes took 17.12019443511963s
Versatility | Languages check for List of Czech data boxes took 300.1239912509918s
Interpretability | Number of blank nodes check for List of Czech data boxes took 13.354904651641846s
Interpretability | RDF structures check for List of Czech data boxes took 0.6502516269683838s
Versatility | Serialization formats check for List of Czech data boxes took 0.8650374412536621s
Availability | RDF dump link check for List of Czech data boxes took 34.89267325401306s
License | MR license check for List of Czech data boxes took 0.7947533130645752s
License | HR license check for List of Czech data boxes took 263.71301531791687s
Amount of data | Number of property check for List of Czech data boxes took 0.15286898612976074s
Understandability | Number of label check for List of Czech data boxes took 5.831471681594849s
Understandability | URI regex check for List of Czech data boxes took 0.6304931640625s
Understandability | Vocabs check for List of Czech data boxes took 0.24933147430419922s
Verifiability | Authors check for List of Czech data boxes took 0.36185145378112793s
Verifiability | Publishers check for List of Czech data boxes took 0.16156578063964844s
Performance | Throughput check for List of Czech data boxes took 10.597172021865845s
Amount of data | Check the number of entities for List of Czech data boxes took 3.171217441558838s
Verifiability | Contribs. check for List of Czech data boxes took 0.2407383918762207s
Interlinking | sameAs chians check for List of Czech data boxes took 0.7090761661529541s
Interlinking | skos check for List of Czech data boxes took 0.29604053497314453s
Interlinking | skos check for List of Czech data boxes took 0.11721229553222656s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.33559560775756836s
Currency | Creation date check for List of Czech data boxes took 1.1020591259002686s
Currency | Modification date check for List of Czech data boxes took 0.11758232116699219s
Rep.Conc. | URIs length for List of Czech data boxes took 174.92614245414734s
Interoperability | New vocabularies check for List of Czech data boxes took 45.6915922164917s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.419116735458374s
Accuracy | Check Functional Property for List of Czech data boxes took 0.1904621124267578s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.18132948875427246s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 56.41681218147278s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.0537853240966797s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.591054677963257s
Consistency | Disjoint class check for List of Czech data boxes took 0.15755939483642578s
Consistency | Check Misplaced properties for List of Czech data boxes took 93.96030950546265s
Consistency | Misplaced classes for List of Czech data boxes took 8.573143005371094s
Consistency | Check Ontology hijacking for List of Czech data boxes took 36.182974100112915s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.416588544845581s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 79.35959601402283s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.9156200885772705s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.8606781959533691s
Security | Sign check for List of Czech data boxes took 0.1295328140258789s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 487.62992334365845s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 1.0792808532714844s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02171945571899414s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0008523464202880859s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 22.504088640213013s
Believability | Calculation of trust value for List of Czech data boxes took 5.9604644775390625e-06s
INFO | --- Analysis for cz-list-of-databoxes took 2343.3095004558563s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10802268981933594s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005917549133300781s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 174.8734962940216s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5826990604400635s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 17.425865173339844s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 16.003035306930542s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.14184617996216s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.676894426345825s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.22191643714904785s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2133650779724121s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 34.4393949508667s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11450815200805664s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 226.58104586601257s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1334066390991211s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.820549249649048s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5006945133209229s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17523908615112305s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.21681928634643555s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.19008326530456543s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.432355165481567s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.2505524158477783s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.20020031929016113s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7634038925170898s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1806199550628662s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1247246265411377s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.45469236373901367s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.420515775680542s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1347043514251709s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 181.45675015449524s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 17.99106740951538s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3688220977783203s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1715233325958252s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15863847732543945s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 57.41659355163574s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0968189239501953s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.667135715484619s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1645052433013916s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 91.1148796081543s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.744458436965942s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 39.28962969779968s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4278690814971924s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 83.91404557228088s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0051183700561523s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.895247220993042s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1279294490814209s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 495.1021361351013s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5178525447845459s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 53.083226919174194s
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 2316.8011174201965s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2854146957397461s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0006594657897949219s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 43.37900137901306s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8098933696746826s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24793505668640137s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5729756355285645s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 23.623365879058838s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4983186721801758s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2668900489807129s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.1891655921936035s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3256058692932129s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.35822272300720215s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.569380521774292s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17031025886535645s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.45373964309692383s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3366060256958008s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20366597175598145s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24908447265625s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2944047451019287s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.600786924362183s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.893013000488281e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15561366081237793s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.21924662590026855s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.29172182083129883s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15629816055297852s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.8114452362060547s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.39064502716064453s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.33446216583251953s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 59.41749382019043s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1552896499633789s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16632318496704102s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18265795707702637s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 44.36526131629944s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.378157138824463s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6483492851257324s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20168042182922363s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8313512802124023s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.490755081176758s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 67.24242329597473s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.687042474746704s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.121127128601074s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.182159423828125s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2133188247680664s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3802306652069092s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1030.9407267570496s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.692124843597412s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8781473636627197s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.123283386230469e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.430511474609375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.4836273193359375e-06s
INFO | --- Analysis for cz-nkod took 65528.249581336975s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.2270047664642334s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.2803943157196045s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.2901763916015625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 5.7220458984375e-06s
INFO | --- Analysis for cz-orders took 3.528963804244995s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.18038415908813477s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.00046706199645996094s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 258.191125869751s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5682015419006348s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 17.369308471679688s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 17.074079751968384s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.11259722709656s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 7.340106725692749s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.2438349723815918s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.38132619857788086s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 34.95405888557434s
License | MR license check for Institutions of public power of the Czech Republic took 0.46302032470703125s
License | HR license check for Institutions of public power of the Czech Republic took 300.1747741699219s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.3443105220794678s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 3.6672496795654297s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.4533390998840332s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.24551630020141602s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.19084596633911133s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.19079947471618652s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.29716444015503s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.027533769607544s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.22020721435546875s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.690190315246582s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.17004871368408203s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.10141324996948242s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.24065494537353516s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.30434322357177734s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.15542960166931152s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 199.81952905654907s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 66.31512451171875s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.4445164203643799s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.15052509307861328s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.15625429153442383s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 76.52753734588623s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0732169151306152s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.728881359100342s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.13044166564941406s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 89.61381840705872s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 8.567351341247559s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 87.69284915924072s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.411606788635254s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 79.63148713111877s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.927657127380371s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.8671989440917969s
Security | Sign check for Institutions of public power of the Czech Republic took 0.14160966873168945s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 516.8568694591522s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 1.1082096099853516s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021138429641723633s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 6.270408630371094e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 61.280842781066895s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-ovm took 2604.194667339325s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.09589886665344238s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2554287910461426s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.361701965332031e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ovm-agendas took 3.180335521697998s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 20.04646944999695s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2674105167388916s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.02101731300354004s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.2479248046875e-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.10724020004272s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7454555034637451s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.27725911140441895s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.02075934410095215s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 8.893013000488281e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 4.650680780410767s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.4270901679992676s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.26653075218200684s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.925612449645996s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.42537569999694824s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.27268505096435547s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 2.9802322387695312e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 5.245208740234375e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.417792558670044s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.11434006690979004s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.24446415901184082s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.2901763916015625e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.196549892425537s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.11214256286621094s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2682459354400635s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020694255828857422s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007679462432861328s
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 1.239776611328125e-05s
INFO | --- Analysis for cz-sidc-drug-prices took 2.682868242263794s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.10832405090332031s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.28488588333129883s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.8432562351226807s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.10769486427307129s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0006084442138671875s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 255.47124481201172s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.6227705478668213s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 15.851910829544067s
Interoperability | New terms check for Summary types of Czech institutions of public power took 17.32804012298584s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1790645122528s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.8849289417266846s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.13229751586914062s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.2978646755218506s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 34.68225646018982s
License | MR license check for Summary types of Czech institutions of public power took 0.10431385040283203s
License | HR license check for Summary types of Czech institutions of public power took 300.122412443161s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.3266632556915283s
Understandability | Number of label check for Summary types of Czech institutions of public power took 4.315697908401489s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.30111217498779297s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.23517489433288574s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.3715860843658447s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.19206690788269043s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.43236756324768s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.0481724739074707s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.20729660987854004s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.7944154739379883s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.13572955131530762s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.10908865928649902s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.24969077110290527s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.362468957901001s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.12943410873413086s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 211.58833646774292s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 52.48631024360657s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.43949079513549805s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.11142134666442871s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.10366082191467285s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 84.71733593940735s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.070108652114868s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6408402919769287s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.28727006912231445s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 88.35152554512024s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 8.698009014129639s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 69.05436420440674s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.3646202087402344s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 78.46613216400146s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.8944804668426514s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 1.6273057460784912s
Security | Sign check for Summary types of Czech institutions of public power took 0.1221163272857666s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 453.03488850593567s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.197716474533081s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 69.69812250137329s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.9604644775390625e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2506.193722963333s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.1044609546661377s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.27959156036376953s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020922183990478516s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.5762786865234375e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 4.158514738082886s
Availability | SPARQL endpoint availability check for State funding providers took 0.11718177795410156s
Availability | VoID file availability check for State funding providers took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for State funding providers took 0.6863181591033936s
Reputation | Calculation of the PageRank for State funding providers took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.0531158447265625e-05s
Believability | Calculation of trust value for State funding providers took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.2514827251434326s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10924601554870605s
Availability | VoID file availability check for Organizations active in R&D took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.7018184661865234s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007183551788330078s
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 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-organizations took 3.825920820236206s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11536765098571777s
Availability | VoID file availability check for R&D Programmes took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.27976346015930176s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.886222839355469e-05s
Believability | Calculation of trust value for R&D Programmes took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.7984957695007324s
Availability | SPARQL endpoint availability check for R&D Projects took 0.11941289901733398s
Availability | VoID file availability check for R&D Projects took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.24692678451538086s
Reputation | Calculation of the PageRank for R&D Projects took 0.02095198631286621s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.363059997558594e-05s
Believability | Calculation of trust value for R&D Projects took 1.5020370483398438e-05s
INFO | --- Analysis for cz-vavai-projects took 2.813593864440918s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10747623443603516s
Availability | VoID file availability check for Institutional research plans took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.29758358001708984s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.814697265625e-05s
Believability | Calculation of trust value for Institutional research plans took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-research-plans took 3.2267987728118896s
Availability | SPARQL endpoint availability check for Results of R&D took 0.10819506645202637s
Availability | VoID file availability check for Results of R&D took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.2776179313659668s
Reputation | Calculation of the PageRank for Results of R&D took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.933906555175781e-05s
Believability | Calculation of trust value for Results of R&D took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-results took 2.7742605209350586s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.10816287994384766s
Availability | VoID file availability check for Tenders in R&D took 0.0008041858673095703s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2558424472808838s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.886222839355469e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.822360038757324s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.315376281738281e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.37058377265930176s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.218650817871094e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 6.198883056640625e-06s
INFO | --- Analysis for czech_addresses took 4.8784003257751465s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 180.507408618927s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2829432487487793s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for DanteLatinLoanwords took 313.9406940937042s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.38649654388427734s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0007097721099853516s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 135.20674633979797s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0287580490112305s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 19.28004264831543s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.13165807723999s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.28740859031677s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.25270748138427734s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.12903046607971191s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.4967834949493408s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.4617879390716553s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2465977668762207s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.28551578521728516s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 46.54837727546692s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.21255874633789062s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 0.7813498973846436s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.5161545276641846s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.2495744228363037s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.24597382545471191s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.23003888130187988s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.274637222290039s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 6.937980651855469e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.2284986972808838s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.41303133964538574s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.8081371784210205s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.24253368377685547s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2774240970611572s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.7297556400299072s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.6337876319885254s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 77.92847108840942s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.22132396697998047s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3463625907897949s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.7173020839691162s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 39.599005937576294s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2755064964294434s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.6525959968566895s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.33916521072387695s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.58184313774109s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.49242353439331s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 46.81872034072876s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5256547927856445s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.177173852920532s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8628382682800293s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2344658374786377s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.2398078441619873s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 10.016604900360107s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.8644084930419922s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02155327796936035s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014901161193847656s
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 7.3909759521484375e-06s
INFO | --- Analysis for data-bnf-fr took 742.962503194809s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.295642614364624s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.26781678199768066s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.532669067382812e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.0067901611328125e-06s
INFO | --- Analysis for data-cnr-it took 4.339735507965088s
Availability | SPARQL endpoint availability check for Data.gov took 1.780066967010498s
Availability | VoID file availability check for Data.gov took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Data.gov took 0.27820658683776855s
Reputation | Calculation of the PageRank for Data.gov took 0.02104806900024414s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.170967102050781e-05s
Believability | Calculation of trust value for Data.gov took 5.7220458984375e-06s
INFO | --- Analysis for data-gov took 18.395136833190918s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.10848426818847656s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.27527737617492676s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.022357463836669922s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.104873657226562e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 5.245208740234375e-06s
INFO | --- Analysis for data-gov-ie took 2.696622610092163s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.363059997558594e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.28943347930908203s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020522594451904297s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.2479248046875e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 5.7220458984375e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.474379539489746s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.776523113250732s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.26830101013183594s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.52587890625e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 5.8650970458984375e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 6.67572021484375e-06s
INFO | --- Analysis for data-hnm-hu took 157.0210099220276s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.11014628410339355s
Availability | VoID file availability check for Climb Dataincubator took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2504284381866455s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.271766662597656e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.0251998901367188e-05s
INFO | --- Analysis for data-incubator-climb took 4.190290212631226s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.27777838706970215s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 8.940696716308594e-05s
Believability | Calculation of trust value for Discogs in RDF took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-discogs took 7.780437707901001s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.14121317863464355s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007891654968261719s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.25965142250061035s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.125999450683594e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 4.76837158203125e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.731896162033081s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.055080413818359375s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.2675619125366211s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.392333984375e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-moseley took 8.354696989059448s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.2558765411376953s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.28492307662963867s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.511543273925781e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.6743669509887695s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.896580696105957s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.24590539932250977s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.416175842285156e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 4.76837158203125e-06s
INFO | --- Analysis for data-incubator-nasa took 8.08208441734314s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.04962301254272461s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2945835590362549s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.414817810058594e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.4907124042510986s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.06563019752502441s
Availability | VoID file availability check for Pokedex data in RDF took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2740180492401123s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 8.96453857421875e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.238024711608887s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.05251336097717285s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.28211259841918945s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.021222352981567383s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.893013000488281e-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.5891945362091064s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.4992244243621826s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006203651428222656s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 111.50942993164062s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.3050997257232666s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 17.01156783103943s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.6354670524597168s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.30078387260437s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.33867073059082s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.1774766445159912s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.5170536041259766s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.4615001678466797s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.41952085494995117s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.46714162826538086s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.36208939552307s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.7332777976989746s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.33583903312683s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.6882927417755127s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.49771666526794434s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.4317452907562256s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.389742374420166s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.600350618362427s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.176399230957031e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.3695697784423828s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.816591739654541s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.38890671730041504s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.425311803817749s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.4664592742919922s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.9018633365631104s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 1.0648760795593262s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 48.009634494781494s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.34184932708740234s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.432140588760376s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.33773136138916016s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 47.25951409339905s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.9906697273254395s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.14430046081543s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.6713385581970215s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 1.1198854446411133s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.17314863204956s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 32.78166389465332s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.4808378219604492s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 2.2210381031036377s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.854163885116577s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.5516717433929443s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.42693233489990234s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.12842130661010742s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.4930882453918457s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.0208432674407959s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 1.9073486328125e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 7.62939453125e-06s
INFO | --- Analysis for data-open-ac-uk took 742.4803092479706s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.7956993579864502s
Availability | VoID file availability check for Persée in RDF took 0.0006403923034667969s
Extra | Recovery of all triples for Persée in RDF took 1.844409465789795s
Performance | Total latancy measurement for Persée in RDF took 0.6538965702056885s
Amount of data | Number of triples check for Persée in RDF took 0.737454891204834s
Interoperability | New terms check for Persée in RDF took 1.9395854473114014s
Versatility | Languages check for Persée in RDF took 120.69520711898804s
Interpretability | Number of blank nodes check for Persée in RDF took 0.3905978202819824s
Interpretability | RDF structures check for Persée in RDF took 0.6329934597015381s
Versatility | Serialization formats check for Persée in RDF took 0.8444349765777588s
Availability | RDF dump link check for Persée in RDF took 0.2729618549346924s
License | MR license check for Persée in RDF took 1.4835679531097412s
License | HR license check for Persée in RDF took 37.74955677986145s
Amount of data | Number of property check for Persée in RDF took 0.1412351131439209s
Understandability | Number of label check for Persée in RDF took 1.8040544986724854s
Understandability | URI regex check for Persée in RDF took 0.8442232608795166s
Understandability | Vocabs check for Persée in RDF took 0.4065985679626465s
Verifiability | Authors check for Persée in RDF took 0.14322352409362793s
Verifiability | Publishers check for Persée in RDF took 0.1325392723083496s
Performance | Throughput check for Persée in RDF took 10.528088808059692s
Amount of data | Check the number of entities for Persée in RDF took 7.343292236328125e-05s
Verifiability | Contribs. check for Persée in RDF took 0.1299581527709961s
Interlinking | sameAs chians check for Persée in RDF took 0.20393109321594238s
Interlinking | skos check for Persée in RDF took 0.6564357280731201s
Interlinking | skos check for Persée in RDF took 0.13379454612731934s
Timeliness | dataset update frequency check for Persée in RDF took 0.6665408611297607s
Currency | Creation date check for Persée in RDF took 0.5278515815734863s
Currency | Modification date check for Persée in RDF took 0.28290867805480957s
Rep.Conc. | URIs length for Persée in RDF took 3.656116247177124s
Interoperability | New vocabularies check for Persée in RDF took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.13260126113891602s
Accuracy | Check Functional Property for Persée in RDF took 0.14229893684387207s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.12846899032592773s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.9625449180603027s
Accuracy | Check White space in annotation for Persée in RDF took 0.03842449188232422s
Accuracy | Check Datatype consistency for Persée in RDF took 0.027080535888671875s
Consistency | Disjoint class check for Persée in RDF took 0.2967956066131592s
Consistency | Check Misplaced properties for Persée in RDF took 2.6164753437042236s
Consistency | Misplaced classes for Persée in RDF took 0.24189972877502441s
Consistency | Check Ontology hijacking for Persée in RDF took 2.085010051727295s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.3576090335845947s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.8600149154663086s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.030981063842773438s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.11997747421264648s
Security | Sign check for Persée in RDF took 0.8296780586242676s
Availability | Check URIs Dereferenciability for Persée in RDF took 1359.8307864665985s
Completeness | Calculation of interlinking completeness for Persée in RDF took 1.206620216369629s
Reputation | Calculation of the PageRank for Persée in RDF took 0.02094101905822754s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007603168487548828s
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 9.5367431640625e-07s
Believability | Calculation of trust value for Persée in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-persee-fr took 1604.5032680034637s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.124641418457031e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.2632420063018799s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.504753112792969e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 1.2159347534179688e-05s
INFO | --- Analysis for data-southampton-ac-uk took 4.247208118438721s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.652353048324585s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0003428459167480469s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.2562892436981201s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011086463928222656s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 6.9141387939453125e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.443017482757568s
Availability | SPARQL endpoint availability check for Open Data Web took 0.29108548164367676s
Availability | VoID file availability check for Open Data Web took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2826566696166992s
Reputation | Calculation of the PageRank for Open Data Web took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 2.7894973754882812e-05s
Believability | Calculation of trust value for Open Data Web took 7.152557373046875e-06s
INFO | --- Analysis for data.odw.tw took 3.1570467948913574s
Availability | SPARQL endpoint availability check for DataFAQs took 3.981590270996094e-05s
Availability | VoID file availability check for DataFAQs took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.28698134422302246s
Reputation | Calculation of the PageRank for DataFAQs took 0.020398855209350586s
Interlinking | Calculation of Degree of Connection for DataFAQs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 2.8371810913085938e-05s
Believability | Calculation of trust value for DataFAQs took 7.3909759521484375e-06s
INFO | --- Analysis for datafaqs took 2.94024395942688s
Availability | SPARQL endpoint availability check for datahub took 9.489059448242188e-05s
Availability | VoID file availability check for datahub took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for datahub took 0.28418612480163574s
Reputation | Calculation of the PageRank for datahub took 0.020289897918701172s
Interlinking | Calculation of Degree of Connection for datahub took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for datahub took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for datahub took 4.506111145019531e-05s
Believability | Calculation of trust value for datahub took 6.67572021484375e-06s
INFO | --- Analysis for datahub took 3.1050808429718018s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 5.778496980667114s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.2629380226135254s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.000957489013671875s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.695487976074219e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 7.867813110351562e-06s
INFO | --- Analysis for datahub-kr-datamap took 15.5438814163208s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.39751315116882324s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2517521381378174s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.200241088867188e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.106231689453125e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.026911973953247s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.437615156173706s
Availability | VoID file availability check for datos-artium-org took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.258023738861084s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011730194091796875s
Believability | Calculation of trust value for datos-artium-org took 7.152557373046875e-06s
INFO | --- Analysis for datos-artium-org took 164.59248685836792s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.9357621669769287s
Availability | VoID file availability check for Datos.bcn.cl took 0.0004017353057861328s
Extra | Recovery of all triples for Datos.bcn.cl took 166.11666345596313s
Performance | Total latancy measurement for Datos.bcn.cl took 261.40114068984985s
Amount of data | Number of triples check for Datos.bcn.cl took 64.71991682052612s
Interoperability | New terms check for Datos.bcn.cl took 62.783464670181274s
Versatility | Languages check for Datos.bcn.cl took 300.9818551540375s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.6022789478302002s
Security | Check HTTPS for Datos.bcn.cl took 62.11344385147095s
Interpretability | RDF structures check for Datos.bcn.cl took 62.5990834236145s
Versatility | Serialization formats check for Datos.bcn.cl took 62.47278690338135s
Availability | RDF dump link check for Datos.bcn.cl took 62.496530055999756s
License | MR license check for Datos.bcn.cl took 62.571919202804565s
License | HR license check for Datos.bcn.cl took 96.8613338470459s
Amount of data | Number of property check for Datos.bcn.cl took 28.207178115844727s
Understandability | Number of label check for Datos.bcn.cl took 63.13466787338257s
Understandability | URI regex check for Datos.bcn.cl took 124.42605209350586s
Understandability | Vocabs check for Datos.bcn.cl took 62.55210995674133s
Verifiability | Authors check for Datos.bcn.cl took 62.52321004867554s
Verifiability | Publishers check for Datos.bcn.cl took 62.533374309539795s
Performance | Throughput check for Datos.bcn.cl took 625.2136850357056s
Amount of data | Check the number of entities for Datos.bcn.cl took 3.719329833984375e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 62.554484128952026s
Interlinking | sameAs chians check for Datos.bcn.cl took 62.503764629364014s
Interlinking | skos check for Datos.bcn.cl took 62.56076645851135s
Interlinking | skos check for Datos.bcn.cl took 62.514153718948364s
Timeliness | dataset update frequency check for Datos.bcn.cl took 62.53187537193298s
Currency | Creation date check for Datos.bcn.cl took 125.10069394111633s
Currency | Modification date check for Datos.bcn.cl took 62.53832983970642s
Rep.Conc. | URIs length for Datos.bcn.cl took 151.29140186309814s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 36.16804218292236s
Accuracy | Check Functional Property for Datos.bcn.cl took 62.5036997795105s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 62.504284620285034s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 82.43834590911865s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.23846650123596191s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2668442726135254s
Consistency | Disjoint class check for Datos.bcn.cl took 42.15550494194031s
Consistency | Check Misplaced properties for Datos.bcn.cl took 128.6520688533783s
Consistency | Misplaced classes for Datos.bcn.cl took 59.82632255554199s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 84.93319535255432s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3975818157196045s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 42.82090973854065s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.3080124855041504s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 57.47025156021118s
Security | Sign check for Datos.bcn.cl took 62.29031705856323s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 12.208600759506226s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.2207846641540527s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02116250991821289s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 8.726119995117188e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.9073486328125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 6.4373016357421875e-06s
INFO | --- Analysis for datos-bcn-cl took 5950.249720573425s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.3407018184661865s
Availability | VoID file availability check for datos.bne.es took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.6859698295593262s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011205673217773438s
Believability | Calculation of trust value for datos.bne.es took 6.9141387939453125e-06s
INFO | --- Analysis for datos-bne-es took 6.36597752571106s
Availability | SPARQL endpoint availability check for dbacademic took 0.16142797470092773s
Availability | VoID file availability check for dbacademic took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for dbacademic took 0.25836849212646484s
Reputation | Calculation of the PageRank for dbacademic took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.170967102050781e-05s
Believability | Calculation of trust value for dbacademic took 5.245208740234375e-06s
INFO | --- Analysis for dbacademic took 3.004333257675171s
Availability | SPARQL endpoint availability check for DBkWik took 0.2193591594696045s
Availability | VoID file availability check for DBkWik took 0.0005421638488769531s
Extra | Recovery of all triples for DBkWik took 2.5448882579803467s
Performance | Total latancy measurement for DBkWik took 0.4226651191711426s
Amount of data | Number of triples check for DBkWik took 11.982427597045898s
Interoperability | New terms check for DBkWik took 2.190692663192749s
Versatility | Languages check for DBkWik took 60.45149374008179s
Interpretability | Number of blank nodes check for DBkWik took 0.15034151077270508s
Interpretability | RDF structures check for DBkWik took 0.20508742332458496s
Versatility | Serialization formats check for DBkWik took 0.190230131149292s
Availability | RDF dump link check for DBkWik took 2.913243293762207s
License | MR license check for DBkWik took 0.2841205596923828s
License | HR license check for DBkWik took 60.489871978759766s
Amount of data | Number of property check for DBkWik took 0.13460755348205566s
Understandability | Number of label check for DBkWik took 2.201878309249878s
Understandability | URI regex check for DBkWik took 0.30077409744262695s
Understandability | Vocabs check for DBkWik took 0.19901490211486816s
Verifiability | Authors check for DBkWik took 0.11797475814819336s
Verifiability | Publishers check for DBkWik took 0.09574127197265625s
Performance | Throughput check for DBkWik took 10.619541883468628s
Amount of data | Check the number of entities for DBkWik took 7.605552673339844e-05s
Verifiability | Contribs. check for DBkWik took 0.11646628379821777s
Interlinking | sameAs chians check for DBkWik took 0.42203307151794434s
Interlinking | skos check for DBkWik took 0.5299654006958008s
Interlinking | skos check for DBkWik took 0.08342623710632324s
Timeliness | dataset update frequency check for DBkWik took 0.19844961166381836s
Currency | Creation date check for DBkWik took 0.4840731620788574s
Currency | Modification date check for DBkWik took 0.19370222091674805s
Rep.Conc. | URIs length for DBkWik took 11.638360023498535s
Interoperability | New vocabularies check for DBkWik took 27.05010485649109s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.1136331558227539s
Accuracy | Check Functional Property for DBkWik took 0.29500889778137207s
Accuracy | Check Inverse Functional Property for DBkWik took 0.26767492294311523s
Accuracy | Check Empty annotation labels for DBkWik took 1.2099814414978027s
Accuracy | Check White space in annotation for DBkWik took 0.023298978805541992s
Accuracy | Check Datatype consistency for DBkWik took 0.02804398536682129s
Consistency | Disjoint class check for DBkWik took 0.10761785507202148s
Consistency | Check Misplaced properties for DBkWik took 12.368530035018921s
Consistency | Misplaced classes for DBkWik took 0.6504793167114258s
Consistency | Check Ontology hijacking for DBkWik took 1.8872706890106201s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.278306007385254s
Consistency | Check Invalid usage of undefined properties for DBkWik took 12.381752490997314s
Conciseness | Check Extensional conciseness for DBkWik took 0.03284120559692383s
Conciseness | Check Intensional conciseness for DBkWik took 0.9093763828277588s
Security | Sign check for DBkWik took 0.3700578212738037s
Availability | Check URIs Dereferenciability for DBkWik took 11.685847520828247s
Completeness | Calculation of interlinking completeness for DBkWik took 0.751819372177124s
Reputation | Calculation of the PageRank for DBkWik took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.390975952148438e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 5.507901906967163s
Believability | Calculation of trust value for DBkWik took 7.152557373046875e-06s
INFO | --- Analysis for dbkwik took 1379.1421298980713s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.291534423828125e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.7512667179107666s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010943412780761719s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.1205673217773438e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 15.4550940990448s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.46944141387939453s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0005552768707275391s
Extra | Recovery of all triples for dblp Knowledge Graph took 56.70950174331665s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.8057668209075928s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.14642047882080078s
Interoperability | New terms check for dblp Knowledge Graph took 2.1504735946655273s
Versatility | Languages check for dblp Knowledge Graph took 30.54572057723999s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.174511671066284s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.16311979293823242s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.17099237442016602s
Availability | RDF dump link check for dblp Knowledge Graph took 0.14459824562072754s
License | MR license check for dblp Knowledge Graph took 0.16428136825561523s
License | HR license check for dblp Knowledge Graph took 30.17487645149231s
Amount of data | Number of property check for dblp Knowledge Graph took 0.16252684593200684s
Understandability | Number of label check for dblp Knowledge Graph took 0.5324358940124512s
Understandability | URI regex check for dblp Knowledge Graph took 0.27861595153808594s
Understandability | Vocabs check for dblp Knowledge Graph took 0.17731666564941406s
Verifiability | Authors check for dblp Knowledge Graph took 0.1478433609008789s
Verifiability | Publishers check for dblp Knowledge Graph took 0.1334846019744873s
Performance | Throughput check for dblp Knowledge Graph took 12.015277862548828s
Amount of data | Check the number of entities for dblp Knowledge Graph took 0.00013399124145507812s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.15528273582458496s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.2070157527923584s
Interlinking | skos check for dblp Knowledge Graph took 0.12979340553283691s
Interlinking | skos check for dblp Knowledge Graph took 0.14946222305297852s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.15978217124938965s
Currency | Creation date check for dblp Knowledge Graph took 0.3620178699493408s
Currency | Modification date check for dblp Knowledge Graph took 0.3256709575653076s
Rep.Conc. | URIs length for dblp Knowledge Graph took 28.088376760482788s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.14078545570373535s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.14560580253601074s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.16826176643371582s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 19.726797103881836s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.061904191970825s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.23356032371521s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.12490653991699219s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.29183268547058105s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 24.29137134552002s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 17780.042103528976s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 4.347738742828369s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.723130226135254s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.18798494338989258s
Security | Sign check for dblp Knowledge Graph took 0.15217065811157227s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 2.466644525527954s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.753861665725708s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.021199941635131836s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0008885860443115234s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 2.765655517578125e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 2.384185791015625e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 7.867813110351562e-06s
INFO | --- Analysis for dblp-kg took 18075.320386648178s
Availability | SPARQL endpoint availability check for dbnary took 0.25478029251098633s
Availability | VoID file availability check for dbnary took 0.0005385875701904297s
Extra | Recovery of all triples for dbnary took 1.8909876346588135s
Performance | Total latancy measurement for dbnary took 0.37447500228881836s
Amount of data | Number of triples check for dbnary took 1.5329582691192627s
Interoperability | New terms check for dbnary took 3.7358124256134033s
Versatility | Languages check for dbnary took 62.05893898010254s
Interpretability | Number of blank nodes check for dbnary took 0.8000547885894775s
Security | Check HTTPS for dbnary took 0.2009873390197754s
Interpretability | RDF structures check for dbnary took 0.19839835166931152s
Versatility | Serialization formats check for dbnary took 0.22298860549926758s
Availability | RDF dump link check for dbnary took 0.06821966171264648s
License | MR license check for dbnary took 0.3613004684448242s
License | HR license check for dbnary took 61.011789083480835s
Amount of data | Number of property check for dbnary took 0.12217521667480469s
Understandability | Number of label check for dbnary took 0.6913771629333496s
Understandability | URI regex check for dbnary took 0.14026427268981934s
Understandability | Vocabs check for dbnary took 0.15802764892578125s
Verifiability | Authors check for dbnary took 0.22518372535705566s
Verifiability | Publishers check for dbnary took 0.16881012916564941s
Performance | Throughput check for dbnary took 10.555339813232422s
Amount of data | Check the number of entities for dbnary took 4.982948303222656e-05s
Verifiability | Contribs. check for dbnary took 0.19446229934692383s
Interlinking | sameAs chians check for dbnary took 0.09386587142944336s
Interlinking | skos check for dbnary took 0.17399239540100098s
Interlinking | skos check for dbnary took 0.08076953887939453s
Timeliness | dataset update frequency check for dbnary took 0.11285614967346191s
Currency | Creation date check for dbnary took 0.2714385986328125s
Currency | Modification date check for dbnary took 0.20317578315734863s
Rep.Conc. | URIs length for dbnary took 11.590002298355103s
Interoperability | New vocabularies check for dbnary took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.11192107200622559s
Accuracy | Check Functional Property for dbnary took 0.1497187614440918s
Accuracy | Check Inverse Functional Property for dbnary took 0.18820810317993164s
Accuracy | Check Empty annotation labels for dbnary took 0.5238845348358154s
Accuracy | Check White space in annotation for dbnary took 0.030184507369995117s
Accuracy | Check Datatype consistency for dbnary took 0.027300119400024414s
Consistency | Disjoint class check for dbnary took 0.1498856544494629s
Consistency | Check Misplaced properties for dbnary took 9.048367738723755s
Consistency | Misplaced classes for dbnary took 0.2293388843536377s
Consistency | Check Ontology hijacking for dbnary took 1.837618350982666s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.341923475265503s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.185738563537598s
Conciseness | Check Extensional conciseness for dbnary took 0.031025409698486328s
Conciseness | Check Intensional conciseness for dbnary took 0.1821134090423584s
Security | Sign check for dbnary took 0.09816884994506836s
Availability | Check URIs Dereferenciability for dbnary took 14.621351480484009s
Completeness | Calculation of interlinking completeness for dbnary took 0.6897087097167969s
Reputation | Calculation of the PageRank for dbnary took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for dbnary took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.6743621826171875e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.6689300537109375e-06s
Believability | Calculation of trust value for dbnary took 7.62939453125e-06s
INFO | --- Analysis for dbnary took 293.4249930381775s
Availability | SPARQL endpoint availability check for DBpedia took 14.692037343978882s
Availability | VoID file availability check for DBpedia took 0.0004169940948486328s
Extra | Recovery of all triples for DBpedia took 61.4041543006897s
Performance | Total latancy measurement for DBpedia took 24.376034021377563s
Amount of data | Number of triples check for DBpedia took 13.73811960220337s
Interoperability | New terms check for DBpedia took 15.36013412475586s
Versatility | Languages check for DBpedia took 36.02665877342224s
Interpretability | Number of blank nodes check for DBpedia took 7.43082857131958s
Security | Check HTTPS for DBpedia took 5.069294691085815s
Interpretability | RDF structures check for DBpedia took 2.051586151123047s
Versatility | Serialization formats check for DBpedia took 25.674448251724243s
Availability | RDF dump link check for DBpedia took 1.5198140144348145s
License | MR license check for DBpedia took 14.835801124572754s
License | HR license check for DBpedia took 56.806471824645996s
Amount of data | Number of property check for DBpedia took 4.461684226989746s
Understandability | Number of label check for DBpedia took 9.457955360412598s
Understandability | URI regex check for DBpedia took 13.23103666305542s
Understandability | Vocabs check for DBpedia took 12.37475299835205s
Verifiability | Authors check for DBpedia took 10.397000312805176s
Verifiability | Publishers check for DBpedia took 13.231969118118286s
Performance | Throughput check for DBpedia took 51.53164601325989s
Amount of data | Check the number of entities for DBpedia took 6.961822509765625e-05s
Verifiability | Contribs. check for DBpedia took 19.353827953338623s
Interlinking | sameAs chians check for DBpedia took 8.044678926467896s
Interlinking | skos check for DBpedia took 13.560282230377197s
Interlinking | skos check for DBpedia took 1.9783985614776611s
Timeliness | dataset update frequency check for DBpedia took 17.306870460510254s
Currency | Creation date check for DBpedia took 10.889360189437866s
Currency | Modification date check for DBpedia took 26.564658641815186s
Rep.Conc. | URIs length for DBpedia took 90.72164225578308s
Interoperability | New vocabularies check for DBpedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 10.407749652862549s
Accuracy | Check Functional Property for DBpedia took 1.7504911422729492s
Accuracy | Check Inverse Functional Property for DBpedia took 3.417106866836548s
Accuracy | Check Empty annotation labels for DBpedia took 39.193400621414185s
Accuracy | Check White space in annotation for DBpedia took 0.030776500701904297s
Accuracy | Check Datatype consistency for DBpedia took 0.02751636505126953s
Consistency | Disjoint class check for DBpedia took 17.123413562774658s
Consistency | Check Misplaced properties for DBpedia took 59.13568568229675s
Consistency | Misplaced classes for DBpedia took 41.117645263671875s
Consistency | Check Ontology hijacking for DBpedia took 42.72219777107239s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.2626006603240967s
Consistency | Check Invalid usage of undefined properties for DBpedia took 20.544917821884155s
Conciseness | Check Extensional conciseness for DBpedia took 0.03096747398376465s
Conciseness | Check Intensional conciseness for DBpedia took 98.94500136375427s
Security | Sign check for DBpedia took 4.349094390869141s
Availability | Check URIs Dereferenciability for DBpedia took 9943.093423366547s
Completeness | Calculation of interlinking completeness for DBpedia took 1.5736589431762695s
Reputation | Calculation of the PageRank for DBpedia took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008983612060546875s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia took 11743.922348737717s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 7.414817810058594e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0003459453582763672s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.2833385467529297s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 7.319450378417969e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 9.366214990615845s
Availability | SPARQL endpoint availability check for DBpedia Commons took 4.408697843551636s
Availability | VoID file availability check for DBpedia Commons took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.26053738594055176s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.866455078125e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-commons took 14.156620740890503s
Availability | SPARQL endpoint availability check for DBpedia in German took 4.3392181396484375e-05s
Availability | VoID file availability check for DBpedia in German took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.2506747245788574s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 7.462501525878906e-05s
Believability | Calculation of trust value for DBpedia in German took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-de took 3.426015853881836s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 11.009383916854858s
Availability | VoID file availability check for DBpedia in Greek took 0.0007631778717041016s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.29537177085876465s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00019240379333496094s
Believability | Calculation of trust value for DBpedia in Greek took 4.5299530029296875e-06s
INFO | --- Analysis for dbpedia-el took 46.88009572029114s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 1.509284257888794s
Availability | VoID file availability check for DBpedia in Spanish took 0.0006399154663085938s
Extra | Recovery of all triples for DBpedia in Spanish took 21.654990911483765s
Performance | Total latancy measurement for DBpedia in Spanish took 13.104557752609253s
Amount of data | Number of triples check for DBpedia in Spanish took 9.349940299987793s
Interoperability | New terms check for DBpedia in Spanish took 6.443459749221802s
Versatility | Languages check for DBpedia in Spanish took 31.604408264160156s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.4014749526977539s
Security | Check HTTPS for DBpedia in Spanish took 0.16833209991455078s
Interpretability | RDF structures check for DBpedia in Spanish took 1.3614943027496338s
Versatility | Serialization formats check for DBpedia in Spanish took 0.5656366348266602s
Availability | RDF dump link check for DBpedia in Spanish took 2.781449794769287s
License | MR license check for DBpedia in Spanish took 4.267579793930054s
License | HR license check for DBpedia in Spanish took 32.75490713119507s
Amount of data | Number of property check for DBpedia in Spanish took 0.34099578857421875s
Understandability | Number of label check for DBpedia in Spanish took 1.82094144821167s
Understandability | URI regex check for DBpedia in Spanish took 0.9030566215515137s
Understandability | Vocabs check for DBpedia in Spanish took 1.2349343299865723s
Verifiability | Authors check for DBpedia in Spanish took 1.8151164054870605s
Verifiability | Publishers check for DBpedia in Spanish took 2.42655611038208s
Performance | Throughput check for DBpedia in Spanish took 26.719300985336304s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.224082946777344e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 2.783327102661133s
Interlinking | sameAs chians check for DBpedia in Spanish took 1.9258055686950684s
Interlinking | skos check for DBpedia in Spanish took 3.6856534481048584s
Interlinking | skos check for DBpedia in Spanish took 2.970551013946533s
Timeliness | dataset update frequency check for DBpedia in Spanish took 3.2881646156311035s
Currency | Creation date check for DBpedia in Spanish took 5.078816890716553s
Currency | Modification date check for DBpedia in Spanish took 6.24290657043457s
Rep.Conc. | URIs length for DBpedia in Spanish took 32.45093631744385s
Interoperability | New vocabularies check for DBpedia in Spanish took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 3.406330108642578s
Accuracy | Check Functional Property for DBpedia in Spanish took 2.025953531265259s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 2.615004539489746s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 14.209170579910278s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.030736923217773438s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.02739739418029785s
Consistency | Disjoint class check for DBpedia in Spanish took 3.8907198905944824s
Consistency | Check Misplaced properties for DBpedia in Spanish took 30.112749099731445s
Consistency | Misplaced classes for DBpedia in Spanish took 12.107468128204346s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 15.627291202545166s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.2669315338134766s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 13.92582654953003s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03388333320617676s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 13.861576557159424s
Security | Sign check for DBpedia in Spanish took 2.799075126647949s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 11.663723468780518s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.32027649879455566s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021184682846069336s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.000949859619140625s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00013637542724609375s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.9073486328125e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-es took 3725.0274846553802s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.2865498065948486s
Availability | VoID file availability check for DBpedia in Basque took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.7178351879119873s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020168304443359375s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.0279159545898438e-05s
Believability | Calculation of trust value for DBpedia in Basque took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-eu took 8.684055805206299s
Availability | SPARQL endpoint availability check for DBpedia in French took 30.09629249572754s
Availability | VoID file availability check for DBpedia in French took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.6864502429962158s
Reputation | Calculation of the PageRank for DBpedia in French took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00010061264038085938s
Believability | Calculation of trust value for DBpedia in French took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-fr took 421.55999517440796s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 4.58344030380249s
Availability | VoID file availability check for DBpedia in Japanese took 4.155153751373291s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.2885735034942627s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010156631469726562s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 2.6226043701171875e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 4.5299530029296875e-06s
INFO | --- Analysis for dbpedia-ja took 101.12716221809387s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.3392181396484375e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.2710564136505127s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.894371032714844e-05s
Believability | Calculation of trust value for dbpedia lite took 4.5299530029296875e-06s
INFO | --- Analysis for dbpedia-lite took 22.40985131263733s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.1484832763671875e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.2939426898956299s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.266334533691406e-05s
Believability | Calculation of trust value for DBpedia-Live took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-live took 3.0879640579223633s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.2740144729614258s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.26256799697875977s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016355514526367188s
Believability | Calculation of trust value for DBpedia in Dutch took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-nl took 3.2348737716674805s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 0.5691981315612793s
Availability | VoID file availability check for DBpedia in Portuguese took 0.001413106918334961s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.26500749588012695s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.130073547363281e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-pt took 3.6053974628448486s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.076957702636719e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.26575350761413574s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 2.9802322387695312e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-spotlight took 3.4852676391601562s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.315376281738281e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.25324392318725586s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.747245788574219e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.873807430267334s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.172325134277344e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.28751492500305176s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.075599670410156e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-wikidata took 3.088782548904419s
Availability | SPARQL endpoint availability check for DBpedia took 4.100799560546875e-05s
Availability | VoID file availability check for DBpedia took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for DBpedia took 0.2564382553100586s
Reputation | Calculation of the PageRank for DBpedia took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for DBpedia took 2.956390380859375e-05s
Believability | Calculation of trust value for DBpedia took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia_ took 3.39577579498291s
Availability | SPARQL endpoint availability check for DBTropes took 4.3392181396484375e-05s
Availability | VoID file availability check for DBTropes took 0.0003705024719238281s
Completeness | Calculation of interlinking completeness for DBTropes took 0.25945186614990234s
Reputation | Calculation of the PageRank for DBTropes took 0.020819425582885742s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.72747802734375e-05s
Believability | Calculation of trust value for DBTropes took 6.4373016357421875e-06s
INFO | --- Analysis for dbtropes took 3.0249054431915283s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.26850318908691406s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 7.152557373046875e-06s
INFO | --- Analysis for dbtune took 2.9827992916107178s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 8.0108642578125e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.26290178298950195s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.8650970458984375e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.579416990280151s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.291534423828125e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.2620692253112793s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020425081253051758s
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.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.361701965332031e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 6.002450704574585s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.860695123672485s
Availability | VoID file availability check for DBTune.org/classical took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.282672643661499s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 8.034706115722656e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-classical took 22.41235613822937s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.345625638961792s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2715597152709961s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.02118062973022461s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.818771362304688e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.1682510375976562e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 27.936370134353638s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.3369882106781s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2837071418762207s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0008699893951416016s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.963180541992188e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.0251998901367188e-05s
INFO | --- Analysis for dbtune-magnatune took 23.91094660758972s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.348777770996094s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.28252553939819336s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011324882507324219s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.909987211227417s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.326689720153809s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2563018798828125s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020287275314331055s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.507469177246094e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-myspace took 17.90762233734131s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.291534423828125e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.2692527770996094s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 7.867813110351562e-06s
INFO | --- Analysis for dclg-openuplabs took 2.9977269172668457s
Availability | SPARQL endpoint availability check for data.dcs took 4.363059997558594e-05s
Availability | VoID file availability check for data.dcs took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for data.dcs took 0.27203917503356934s
Reputation | Calculation of the PageRank for data.dcs took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.461143493652344e-05s
Believability | Calculation of trust value for data.dcs took 7.3909759521484375e-06s
INFO | --- Analysis for dcs-sheffield took 2.5869643688201904s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.172325134277344e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.27735352516174316s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.02032160758972168s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 2.7894973754882812e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 7.3909759521484375e-06s
INFO | --- Analysis for de-budget took 2.8959648609161377s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.291534423828125e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2602403163909912s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.4332275390625e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.62939453125e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.779048442840576s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 5.459785461425781e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.24959945678710938s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.76837158203125e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 6.4373016357421875e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.5596604347229s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.2438507080078125e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0003116130828857422s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.25705647468566895s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.1948089599609375e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 8.821487426757812e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.9259679317474365s
Availability | SPARQL endpoint availability check for Demografie took 3.9577484130859375e-05s
Availability | VoID file availability check for Demografie took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Demografie took 0.2700676918029785s
Reputation | Calculation of the PageRank for Demografie took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Demografie took 2.9325485229492188e-05s
Believability | Calculation of trust value for Demografie took 7.3909759521484375e-06s
INFO | --- Analysis for demografie took 2.831773519515991s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.291534423828125e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.2543148994445801s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.528594970703125e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 5.9604644775390625e-06s
INFO | --- Analysis for desaparecidos took 2.7502431869506836s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.363059997558594e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2628612518310547s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.72747802734375e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 6.4373016357421875e-06s
INFO | --- Analysis for deustoentrepreneurship took 5.082486152648926s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.1961669921875e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.27321934700012207s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007755756378173828s
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 9.775161743164062e-06s
INFO | --- Analysis for deustotech took 5.698028802871704s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3975834846496582s
Availability | VoID file availability check for Deutsche Biographie took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.2973177433013916s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.03276991844177246s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0015594959259033203s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 6.198883056640625e-05s
Believability | Calculation of trust value for Deutsche Biographie took 6.9141387939453125e-06s
INFO | --- Analysis for deutsche-biographie took 4.296465158462524s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 5.888938903808594e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.00035309791564941406s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.25948071479797363s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 6.9141387939453125e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 3.909693717956543s
Availability | SPARQL endpoint availability check for dev8d took 4.601478576660156e-05s
Availability | VoID file availability check for dev8d took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for dev8d took 0.26392245292663574s
Reputation | Calculation of the PageRank for dev8d took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.699562072753906e-05s
Believability | Calculation of trust value for dev8d took 6.4373016357421875e-06s
INFO | --- Analysis for dev8d took 11.307397365570068s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.155839920043945s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.26027989387512207s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.555152893066406e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 6.67572021484375e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.59257507324219s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.2438507080078125e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.2986946105957031s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.314018249511719e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 7.867813110351562e-06s
INFO | --- Analysis for DHSVM took 14.41417670249939s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.172325134277344e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0003161430358886719s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.27733755111694336s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.123283386230469e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 7.62939453125e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.934190273284912s
Availability | SPARQL endpoint availability check for Diavgeia took 4.482269287109375e-05s
Availability | VoID file availability check for Diavgeia took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.26217031478881836s
Reputation | Calculation of the PageRank for Diavgeia took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.559226989746094e-05s
Believability | Calculation of trust value for Diavgeia took 5.245208740234375e-06s
INFO | --- Analysis for diavgeia took 5.6089701652526855s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0003571510314941406s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.2656059265136719s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011610984802246094s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 6.198883056640625e-06s
INFO | --- Analysis for didactalia took 19.977234840393066s
Availability | SPARQL endpoint availability check for diigo.feed took 4.124641418457031e-05s
Availability | VoID file availability check for diigo.feed took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.29337072372436523s
Reputation | Calculation of the PageRank for diigo.feed took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for diigo.feed took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.86102294921875e-05s
Believability | Calculation of trust value for diigo.feed took 7.152557373046875e-06s
INFO | --- Analysis for diigo-feed took 2.954434394836426s
Availability | SPARQL endpoint availability check for DisGeNET took 1.4454140663146973s
Availability | VoID file availability check for DisGeNET took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.2682015895843506s
Reputation | Calculation of the PageRank for DisGeNET took 0.020951509475708008s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.0001628398895263672s
Believability | Calculation of trust value for DisGeNET took 6.9141387939453125e-06s
INFO | --- Analysis for disgenet took 9.264008283615112s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.00543212890625e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.27664947509765625s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.0517578125e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for disk took 2.873189926147461s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.3392181396484375e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.2456197738647461s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.020887374877929688s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 2.9087066650390625e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for distritos-zaragoza took 2.9239161014556885s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.291534423828125e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.25847363471984863s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 2.9802322387695312e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 6.4373016357421875e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 9.127764463424683s
Availability | SPARQL endpoint availability check for DM2E took 5.4836273193359375e-05s
Availability | VoID file availability check for DM2E took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for DM2E took 0.25096869468688965s
Reputation | Calculation of the PageRank for DM2E took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011110305786132812s
Believability | Calculation of trust value for DM2E took 7.3909759521484375e-06s
INFO | --- Analysis for dm2e took 3.1263251304626465s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.7206878662109375e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.26208972930908203s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.0517578125e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.3909759521484375e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.8849284648895264s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.1878879070281982s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.32295989990234375s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015854835510253906s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 6.9141387939453125e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 8.269821643829346s
Availability | SPARQL endpoint availability check for DOAP Store took 4.172325134277344e-05s
Availability | VoID file availability check for DOAP Store took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.27155184745788574s
Reputation | Calculation of the PageRank for DOAP Store took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for DOAP Store took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 2.9802322387695312e-05s
Believability | Calculation of trust value for DOAP Store took 8.106231689453125e-06s
INFO | --- Analysis for doap_store took 3.0569214820861816s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.2438507080078125e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.28272414207458496s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.175041198730469e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 4.5299530029296875e-06s
INFO | --- Analysis for doi took 8.709664106369019s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.267692565917969e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.2433617115020752s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020122766494750977s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.9802322387695312e-05s
Believability | Calculation of trust value for Driggu Florentino took 7.3909759521484375e-06s
INFO | --- Analysis for Driggu took 3.2752091884613037s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.056416273117065s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.26639533042907715s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.600120544433594e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.239776611328125e-05s
INFO | --- Analysis for drug-data-hifm took 37.55572175979614s
Availability | SPARQL endpoint availability check for dspace took 4.076957702636719e-05s
Availability | VoID file availability check for dspace took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for dspace took 0.2731204032897949s
Reputation | Calculation of the PageRank for dspace took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for dspace took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for dspace took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for dspace took 2.8371810913085938e-05s
Believability | Calculation of trust value for dspace took 6.9141387939453125e-06s
INFO | --- Analysis for dspace took 2.954854965209961s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.2438507080078125e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2582716941833496s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 2.7894973754882812e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 7.152557373046875e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.985816478729248s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.0439567565918s
Availability | VoID file availability check for MetaLex Document Server took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.27764129638671875s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 2.86102294921875e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.62939453125e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 554.36368060112s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.102804183959961s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0023071765899658203s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.2581658363342285s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.8623809814453125e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.62939453125e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 11.173772096633911s
Availability | SPARQL endpoint availability check for DWS-Group took 4.363059997558594e-05s
Availability | VoID file availability check for DWS-Group took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.7027451992034912s
Reputation | Calculation of the PageRank for DWS-Group took 0.021136760711669922s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010347366333007812s
Believability | Calculation of trust value for DWS-Group took 6.67572021484375e-06s
INFO | --- Analysis for dws-group took 3.4077794551849365s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 8.869171142578125e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.00036835670471191406s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.36390233039855957s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.02101898193359375s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.9087066650390625e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 7.152557373046875e-06s
INFO | --- Analysis for E1 took 5.565305471420288s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.07305741310119629s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2800769805908203s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.021356821060180664s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00014662742614746094s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-alaska took 2.9037983417510986s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.044510841369628906s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.280346155166626s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020711898803710938s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.841255187988281e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-cau took 2.5872058868408203s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.04626798629760742s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2709953784942627s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02266716957092285s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 7.534027099609375e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.4868483543395996s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.03869938850402832s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2531764507293701s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02020263671875s
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.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.632110595703125e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-cdrewu took 2.4305553436279297s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.03887295722961426s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0003533363342285156s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.28240013122558594s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02055501937866211s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.0001347064971923828s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.5070905685424805s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.03925728797912598s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.00040030479431152344s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2743983268737793s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.702278137207031e-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.4730911254882812s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.042581796646118164s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.28057169914245605s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020747900009155273s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00014328956604003906s
Believability | Calculation of trust value for eagle-i @ Harvard University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-harvard took 2.4741971492767334s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.04975605010986328s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.00035858154296875s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.31548142433166504s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012421607971191406s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.5974044799804688e-05s
INFO | --- Analysis for eagle-i-hawaii took 2.5733091831207275s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.042859554290771484s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.28473424911499023s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.413459777832031e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-howard took 2.528014659881592s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.028224706649780273s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.28270578384399414s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020814895629882812s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.05718994140625e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.558009624481201s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.05329775810241699s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.27805590629577637s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011682510375976562s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-jsu took 2.548231363296509s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.04769396781921387s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.2725963592529297s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.8623809814453125e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-meharry took 2.4966959953308105s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.04920077323913574s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2947061061859131s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.703636169433594e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-montana took 2.5429036617279053s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.045497894287109375s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.26891446113586426s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020754575729370117s
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.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.965896606445312e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-msm took 2.4636027812957764s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.042694807052612305s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2707972526550293s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.0001304149627685547s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.8358230590820312e-05s
INFO | --- Analysis for eagle-i-ohsu took 2.5008983612060547s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.044203996658325195s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2732431888580322s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.67572021484375e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-psm took 2.441551923751831s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.051219940185546875s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.000579833984375s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.25388050079345703s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007333755493164062s
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 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-tsu took 2.529857635498047s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.03239107131958008s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.27330899238586426s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.523817300796509s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.07460737228393555s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.25415706634521484s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020390987396240234s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.965896606445312e-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.5005130767822266s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.06556367874145508s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0003845691680908203s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2778968811035156s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00072479248046875s
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 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-upr took 2.505082368850708s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.03809165954589844s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00036835670471191406s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.2805821895599365s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.021492481231689453s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.198883056640625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-utep took 2.479515790939331s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.04551386833190918s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.283719539642334s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.009506225585938e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-utsa took 2.463545322418213s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.18124890327453613s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00037789344787597656s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.25691843032836914s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020822525024414062s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.942054748535156e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.661445140838623s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.04592728614807129s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2539818286895752s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.510185241699219e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-xula took 2.53712797164917s
Availability | SPARQL endpoint availability check for Emergency situation took 0.8451430797576904s
Availability | VoID file availability check for Emergency situation took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.26592159271240234s
Reputation | Calculation of the PageRank for Emergency situation took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.792213439941406e-05s
Believability | Calculation of trust value for Emergency situation took 6.9141387939453125e-06s
INFO | --- Analysis for Earthquake took 3.873187780380249s
Availability | SPARQL endpoint availability check for ESO took 0.6582019329071045s
Availability | VoID file availability check for ESO took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for ESO took 0.24347782135009766s
Reputation | Calculation of the PageRank for ESO took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for ESO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for ESO took 8.225440979003906e-05s
Believability | Calculation of trust value for ESO took 9.298324584960938e-06s
INFO | --- Analysis for Earthquake_case took 4.135924577713013s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.20680022239685059s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2546563148498535s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010085105895996094s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for ecb-linked-data took 2.611135959625244s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.299196004867554s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.287442684173584s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.743171691894531e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.4836273193359375e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 10.207500457763672s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 2.1111063957214355s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2502000331878662s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.723403930664062e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.776882171630859s
Availability | SPARQL endpoint availability check for ECLAP took 20.616173028945923s
Availability | VoID file availability check for ECLAP took 0.000308990478515625s
Completeness | Calculation of interlinking completeness for ECLAP took 0.2580909729003906s
Reputation | Calculation of the PageRank for ECLAP took 0.021839380264282227s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.482269287109375e-05s
Believability | Calculation of trust value for ECLAP took 6.9141387939453125e-06s
INFO | --- Analysis for eclap took 53.01678252220154s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.482269287109375e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0004093647003173828s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2787322998046875s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.1920928955078125e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 7.152557373046875e-06s
INFO | --- Analysis for ECNU-GISer took 4.318460941314697s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.2438507080078125e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.26019787788391113s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.221366882324219e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.152557373046875e-06s
INFO | --- Analysis for ecs took 2.5491623878479004s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.2438507080078125e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0009157657623291016s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.2555522918701172s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.021010398864746094s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0008842945098876953s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.361701965332031e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 7.62939453125e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.927084445953369s
Availability | SPARQL endpoint availability check for Edublogs took 4.315376281738281e-05s
Availability | VoID file availability check for Edublogs took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Edublogs took 0.2925570011138916s
Reputation | Calculation of the PageRank for Edublogs took 0.02015852928161621s
Interlinking | Calculation of Degree of Connection for Edublogs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Edublogs took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.560585021972656e-05s
Believability | Calculation of trust value for Edublogs took 1.1205673217773438e-05s
INFO | --- Analysis for edublogs took 3.292431592941284s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5274341106414795s
Availability | VoID file availability check for education.data.gov.uk took 0.0003147125244140625s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.29279661178588867s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.726119995117188e-05s
Believability | Calculation of trust value for education.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for education-data-gov-uk took 4.9023706912994385s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2762463092803955s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.021085023880004883s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.266334533691406e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 8.344650268554688e-06s
INFO | --- Analysis for education-openuplabs took 2.9705519676208496s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.54157543182373s
Availability | VoID file availability check for Educational programs - SISVU took 0.0008916854858398438s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.371690034866333s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02447819709777832s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.173683166503906e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.152557373046875e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1322.8705422878265s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.896040678024292s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.274538516998291s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.600120544433594e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 8.821487426757812e-06s
INFO | --- Analysis for eea took 10.486829280853271s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.6013987064361572s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.28009819984436035s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.269050598144531e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.0067901611328125e-06s
INFO | --- Analysis for eea-rod took 5.876622676849365s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.44997143745422363s
Availability | VoID file availability check for EEA Vocabularies took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.24388909339904785s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.153915405273438e-05s
Believability | Calculation of trust value for EEA Vocabularies took 7.3909759521484375e-06s
INFO | --- Analysis for eea-vocabularies took 6.071840524673462s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 8.916854858398438e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.27967047691345215s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 2.86102294921875e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for ege-university-linked-open-data took 3.5686919689178467s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.4221935272216797s
Availability | VoID file availability check for E-Government Ontology took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.27160167694091797s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020360708236694336s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for E-Government Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for EGovOntology took 3.7550647258758545s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5248773097991943s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005781650543212891s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.1077475547790527s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3338611125946045s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9083447456359863s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9650828838348389s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.36954927444458s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.899930000305176s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.680835485458374s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8880875110626221s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2855405807495117s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7252743244171143s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 7.951509952545166s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.31378650665283203s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.630603551864624s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6731870174407959s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.30034899711608887s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4866635799407959s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3077723979949951s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.689328908920288s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.152557373046875e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.40507006645202637s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3127586841583252s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7634000778198242s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23090434074401855s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9698305130004883s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6086721420288086s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5750415325164795s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.792646884918213s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2811908721923828s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3686549663543701s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.37947821617126465s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2378170490264893s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030013561248779297s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.028438568115234375s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4547696113586426s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.5709333419799805s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4512457847595215s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.8958585262298584s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2903871536254883s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.555994749069214s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.033075809478759766s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4536569118499756s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.42347216606140137s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3255.861077070236s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.680903673171997s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 6.67572021484375e-06s
INFO | --- Analysis for ei2a took 19706.628613948822s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.315376281738281e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2497100830078125s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.021324634552001953s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0008268356323242188s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00013756752014160156s
Believability | Calculation of trust value for EIONET RDF Data took 5.245208740234375e-06s
INFO | --- Analysis for eionet-rdf took 4.256289720535278s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.410743713378906e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0003414154052734375s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.28045034408569336s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.075599670410156e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 6.9141387939453125e-06s
INFO | --- Analysis for ElgooG_ took 2.820840835571289s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.315376281738281e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.7168214321136475s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.02072429656982422s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 3.147125244140625e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.62939453125e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 4.34557318687439s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.23097538948059s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.26131534576416016s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.295608520507812e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 5.4836273193359375e-06s
INFO | --- Analysis for elviajero took 25.04114031791687s
Availability | SPARQL endpoint availability check for EMN took 4.220008850097656e-05s
Availability | VoID file availability check for EMN took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for EMN took 0.27094149589538574s
Reputation | Calculation of the PageRank for EMN took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for EMN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EMN took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for EMN took 4.100799560546875e-05s
Believability | Calculation of trust value for EMN took 7.62939453125e-06s
INFO | --- Analysis for emn took 2.7230398654937744s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 6.651878356933594e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.26628756523132324s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.021138429641723633s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.2928924560546875e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-co2emission took 2.4455177783966064s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.410743713378906e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2485213279724121s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.52587890625e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0010364055633544922s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 5.221366882324219e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-crime took 2.4708456993103027s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 5.078315734863281e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2707400321960449s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 8.821487426757812e-06s
INFO | --- Analysis for enakting-energy took 2.411257028579712s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 0.0006175041198730469s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.25499987602233887s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 8.869171142578125e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 4.291534423828125e-06s
INFO | --- Analysis for enakting-mortality took 2.8110713958740234s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.887580871582031e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.25542736053466797s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.600120544433594e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 8.821487426757812e-06s
INFO | --- Analysis for enakting-nhs took 2.857130527496338s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.26694536209106445s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.245208740234375e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-population took 2.43548321723938s
Availability | SPARQL endpoint availability check for Enel Shops took 4.00543212890625e-05s
Availability | VoID file availability check for Enel Shops took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.269500732421875s
Reputation | Calculation of the PageRank for Enel Shops took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for Enel Shops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Enel Shops took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.075599670410156e-05s
Believability | Calculation of trust value for Enel Shops took 6.198883056640625e-06s
INFO | --- Analysis for enel-shops took 2.964953660964966s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.029273986816406e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.27112770080566406s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.0517578125e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 5.7220458984375e-06s
INFO | --- Analysis for energy-efficiency took 2.9169163703918457s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.2687568664550781s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 5.4836273193359375e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.961737632751465s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.25958681106567383s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 5.245208740234375e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.948183059692383s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 5.316734313964844e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.2735416889190674s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.8923325538635254s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.363059997558594e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.0003044605255126953s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.2645096778869629s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.170967102050781e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.9348032474517822s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.0003039836883544922s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.27726244926452637s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020426511764526367s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 2.8133392333984375e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.9675257205963135s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.506111145019531e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.24615097045898438s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020306825637817383s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 2.8371810913085938e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.8593688011169434s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.4345855712890625e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.00034236907958984375s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.26739001274108887s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.24249267578125e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.9520232677459717s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.9250123500823975s
Availability | VoID file availability check for English Heritage Periods List took 0.0004734992980957031s
Extra | Recovery of all triples for English Heritage Periods List took 0.4062063694000244s
Performance | Total latancy measurement for English Heritage Periods List took 2.0070509910583496s
Amount of data | Number of triples check for English Heritage Periods List took 0.5525774955749512s
Versatility | Languages check for English Heritage Periods List took 0.37221741676330566s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.6108336448669434s
Security | Check HTTPS for English Heritage Periods List took 0.28996706008911133s
Interpretability | RDF structures check for English Heritage Periods List took 0.3661355972290039s
Versatility | Serialization formats check for English Heritage Periods List took 0.7734169960021973s
Availability | RDF dump link check for English Heritage Periods List took 0.4288773536682129s
License | MR license check for English Heritage Periods List took 0.5896401405334473s
License | HR license check for English Heritage Periods List took 0.42430758476257324s
Amount of data | Number of property check for English Heritage Periods List took 0.4409778118133545s
Understandability | Number of label check for English Heritage Periods List took 0.5547606945037842s
Understandability | URI regex check for English Heritage Periods List took 0.8343262672424316s
Understandability | Vocabs check for English Heritage Periods List took 0.4429340362548828s
Verifiability | Authors check for English Heritage Periods List took 0.5550568103790283s
Verifiability | Publishers check for English Heritage Periods List took 0.5523049831390381s
Performance | Throughput check for English Heritage Periods List took 13.16652774810791s
Amount of data | Check the number of entities for English Heritage Periods List took 6.747245788574219e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.440082311630249s
Interlinking | sameAs chians check for English Heritage Periods List took 0.4172985553741455s
Interlinking | skos check for English Heritage Periods List took 0.4499952793121338s
Interlinking | skos check for English Heritage Periods List took 0.4242253303527832s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.48400330543518066s
Currency | Creation date check for English Heritage Periods List took 0.8135645389556885s
Currency | Modification date check for English Heritage Periods List took 0.8694641590118408s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8183567523956299s
Interoperability | New vocabularies check for English Heritage Periods List took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.45763611793518066s
Accuracy | Check Functional Property for English Heritage Periods List took 0.430112361907959s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.39098668098449707s
Consistency | Disjoint class check for English Heritage Periods List took 0.3952295780181885s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.43044114112854004s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.7091727256774902s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001404285430908203s
Security | Sign check for English Heritage Periods List took 0.47039341926574707s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.28670501708984375s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.361701965332031e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 7.867813110351562e-06s
INFO | --- Analysis for english-heritage-periods-list took 62.486487865448s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 1.015270709991455s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.5793778896331787s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.2525672912597656s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02034163475036621s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.266334533691406e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 5.0067901611328125e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 7.737710952758789s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.8278777599334717s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.8007233142852783s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.270611047744751s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.361701965332031e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.245208740234375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 7.643819570541382s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.220008850097656e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.28880739212036133s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 2.9325485229492188e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 7.152557373046875e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.962071657180786s
Availability | SPARQL endpoint availability check for English WordNet took 4.2438507080078125e-05s
Availability | VoID file availability check for English WordNet took 0.000978231430053711s
Completeness | Calculation of interlinking completeness for English WordNet took 0.24381542205810547s
Reputation | Calculation of the PageRank for English WordNet took 0.022171497344970703s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0009107589721679688s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.790855407714844e-05s
Believability | Calculation of trust value for English WordNet took 6.67572021484375e-06s
INFO | --- Analysis for english-wordnet took 3.459851026535034s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.029273986816406e-05s
Availability | VoID file availability check for English Heritage Places took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.253631591796875s
Reputation | Calculation of the PageRank for English Heritage Places took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 2.8133392333984375e-05s
Believability | Calculation of trust value for English Heritage Places took 7.3909759521484375e-06s
INFO | --- Analysis for englishheritage_places took 2.9143242835998535s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.18060779571533203s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.27196216583251953s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.726119995117188e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 6.67572021484375e-06s
INFO | --- Analysis for enipedia took 2.568267345428467s
Availability | SPARQL endpoint availability check for Enslaved.org took 5.030632019042969e-05s
Availability | VoID file availability check for Enslaved.org took 0.0003886222839355469s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2512698173522949s
Reputation | Calculation of the PageRank for Enslaved.org took 0.022179603576660156s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0008311271667480469s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.2901763916015625e-05s
Believability | Calculation of trust value for Enslaved.org took 7.152557373046875e-06s
INFO | --- Analysis for enslaved.org took 4.675131559371948s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.06627202033996582s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.25095176696777344s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 4.982948303222656e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 6.9141387939453125e-06s
INFO | --- Analysis for entice-graph took 2.4900147914886475s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.363059997558594e-05s
Availability | VoID file availability check for Entrez Gene took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2399730682373047s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.552436828613281e-05s
Believability | Calculation of trust value for Entrez Gene took 6.9141387939453125e-06s
INFO | --- Analysis for entrez_gene took 27.759377479553223s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.315376281738281e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.00032901763916015625s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.2614471912384033s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020097732543945312s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 2.8371810913085938e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.3909759521484375e-06s
INFO | --- Analysis for entrez_gene_extract took 2.8287370204925537s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.1151351928710938s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.00033402442932128906s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.27649807929992676s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 4.9591064453125e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 4.291534423828125e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 11.880675554275513s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.3039417266845703s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.25901365280151367s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.5299530029296875e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 5.0067901611328125e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.697576761245728s
Availability | SPARQL endpoint availability check for EARTh took 271.58386635780334s
Availability | VoID file availability check for EARTh took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for EARTh took 0.26854991912841797s
Reputation | Calculation of the PageRank for EARTh took 0.032483577728271484s
Interlinking | Calculation of Degree of Connection for EARTh took 3.6716461181640625e-05s
Interlinking | Calculation of Centrality for EARTh took 0.001310110092163086s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00013446807861328125s
Believability | Calculation of trust value for EARTh took 7.3909759521484375e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 565.1109311580658s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.5907940864562988s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0002627372741699219s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 122.99889826774597s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.9565722942352295s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 8.054215669631958s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 13.927164316177368s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.2424831390381s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 3.2611305713653564s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.24268436431884766s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 9.559343576431274s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.27418994903564453s
License | MR license check for Micka (EO metadata) @PSNC took 0.5353753566741943s
License | HR license check for Micka (EO metadata) @PSNC took 300.2213463783264s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.31929588317871094s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 2.287371873855591s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.7547123432159424s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.3756561279296875s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.20017337799072266s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.24712634086608887s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.40383505821228s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 7.200241088867188e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.18600225448608398s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.21304702758789062s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4575021266937256s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4431614875793457s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 11.501865863800049s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.49782466888427734s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.20809435844421387s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 157.57444167137146s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.19594383239746094s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.3892486095428467s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.35602283477783203s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 39.626821994781494s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.701014280319214s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.623800039291382s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.2108302116394043s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 82.12407112121582s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.540548086166382s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 39.608070373535156s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.3541278839111328s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 81.54929399490356s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.760631561279297s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5294702053070068s
Security | Sign check for Micka (EO metadata) @PSNC took 0.9656784534454346s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 10.341706275939941s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 1.013335943222046s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021209716796875s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.6716461181640625e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 7.62939453125e-06s
INFO | --- Analysis for EO_metadata took 2273.5861587524414s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.649162292480469e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.7244093418121338s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.021429777145385742s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.170967102050781e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 6.9141387939453125e-06s
INFO | --- Analysis for EOKP-Datasets took 4.698397159576416s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.57763671875e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.27054715156555176s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020421743392944336s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.409385681152344e-05s
Believability | Calculation of trust value for EPA-CDR took 5.0067901611328125e-06s
INFO | --- Analysis for epa-cdr took 9.750006914138794s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.792213439941406e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.2857785224914551s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020170927047729492s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.128715515136719e-05s
Believability | Calculation of trust value for EPA-FRS took 5.0067901611328125e-06s
INFO | --- Analysis for epa-frs took 8.112756252288818s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.649162292480469e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.24834203720092773s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.337860107421875e-05s
Believability | Calculation of trust value for EPA-RCRA took 4.5299530029296875e-06s
INFO | --- Analysis for epa-rcra took 8.224533796310425s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.601478576660156e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.3012421131134033s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.414817810058594e-05s
Believability | Calculation of trust value for EPA-SRS took 4.76837158203125e-06s
INFO | --- Analysis for epa-srs took 8.797918796539307s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.220008850097656e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.27049803733825684s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020233631134033203s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.5762786865234375e-05s
Believability | Calculation of trust value for EPA-TRI took 4.76837158203125e-06s
INFO | --- Analysis for epa-tri took 7.563130617141724s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.029273986816406e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.2626044750213623s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.2479248046875e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 7.62939453125e-06s
INFO | --- Analysis for epo took 2.8845860958099365s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.03366398811340332s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.29133057594299316s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00013065338134765625s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.5085442066192627s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.5733497142791748s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.2699580192565918s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.344650268554688e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 6.67572021484375e-06s
INFO | --- Analysis for eprtr took 3.731072425842285s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 1.276418924331665s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.25661468505859375s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.170967102050781e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 6.67572021484375e-06s
INFO | --- Analysis for ERAKG took 3.7638514041900635s
Availability | SPARQL endpoint availability check for reg took 4.315376281738281e-05s
Availability | VoID file availability check for reg took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for reg took 0.26728010177612305s
Reputation | Calculation of the PageRank for reg took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for reg took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for reg took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for reg took 1.0967254638671875e-05s
Believability | Calculation of trust value for reg took 6.9141387939453125e-06s
INFO | --- Analysis for erg took 2.355311870574951s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.27925801277160645s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.3011176586151123s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 2.9087066650390625e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 5.0067901611328125e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.9919240474700928s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 5.316734313964844e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0007691383361816406s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2904810905456543s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02031254768371582s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.821487426757812e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 4.76837158203125e-06s
INFO | --- Analysis for esd-standards took 4.074077606201172s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.410743713378906e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.26164937019348145s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.104873657226562e-05s
Believability | Calculation of trust value for ESD-Toolkit took 4.5299530029296875e-06s
INFO | --- Analysis for esd-toolkit took 3.4044318199157715s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.7206878662109375e-05s
Availability | VoID file availability check for Dataset Esis took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.2808992862701416s
Reputation | Calculation of the PageRank for Dataset Esis took 0.02259993553161621s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0010592937469482422s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.218650817871094e-05s
Believability | Calculation of trust value for Dataset Esis took 6.9141387939453125e-06s
INFO | --- Analysis for esislearning took 2.876356840133667s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 5.364418029785156e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.30753564834594727s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020226240158081055s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 2.6464462280273438e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 6.67572021484375e-06s
INFO | --- Analysis for ESV took 23.24817943572998s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5206773281097412s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0012526512145996094s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.2669687271118164s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020233154296875s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.409385681152344e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.789410352706909s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 4.237450838088989s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.25513601303100586s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 9.107589721679688e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 6.67572021484375e-06s
INFO | --- Analysis for eu-agencies-bodies took 12.249530553817749s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 4.1484832763671875e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.26212620735168457s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.021069765090942383s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 2.9802322387695312e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 6.9141387939453125e-06s
INFO | --- Analysis for eu-dgt-tm took 3.1125648021698s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.1961669921875e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.00095367431640625s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.26602721214294434s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020134687423706055s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.510185241699219e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 6.4373016357421875e-06s
INFO | --- Analysis for eu-institutions took 5.564652919769287s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.7403838634490967s
Availability | VoID file availability check for EU Parliament Media Library took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.28324174880981445s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.218650817871094e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 4.5299530029296875e-06s
INFO | --- Analysis for eu-parliament-media took 6.707370042800903s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.6900820732116699s
Availability | VoID file availability check for EU Who Is Who took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2821815013885498s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.021982431411743164s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.001010894775390625s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.910064697265625e-05s
Believability | Calculation of trust value for EU Who Is Who took 5.245208740234375e-06s
INFO | --- Analysis for eu-who-is-who took 8.951351165771484s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.7194571495056152s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.24743437767028809s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020827054977416992s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.9577484130859375e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for eumida-linked-data took 7.020114183425903s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.31748390197753906s
Availability | VoID file availability check for European Nature Information System took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.27275943756103516s
Reputation | Calculation of the PageRank for European Nature Information System took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00011134147644042969s
Believability | Calculation of trust value for European Nature Information System took 7.152557373046875e-06s
INFO | --- Analysis for eunis took 11.275434255599976s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 3.867921829223633s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.2637460231781006s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 8.177757263183594e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for eur-lex-rdf took 11.166396379470825s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.7331056594848633s
Availability | VoID file availability check for Standard Eurobarometer took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2637801170349121s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020700931549072266s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.220008850097656e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 4.291534423828125e-06s
INFO | --- Analysis for eurobarometer-standard took 7.115874290466309s
Availability | SPARQL endpoint availability check for European Election Results took 0.7099387645721436s
Availability | VoID file availability check for European Election Results took 0.0008344650268554688s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2871124744415283s
Reputation | Calculation of the PageRank for European Election Results took 0.020844697952270508s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.62396240234375e-05s
Believability | Calculation of trust value for European Election Results took 5.9604644775390625e-06s
INFO | --- Analysis for european-election-results took 7.040075778961182s
Availability | SPARQL endpoint availability check for EPO patents took 0.43816709518432617s
Availability | VoID file availability check for EPO patents took 0.0005447864532470703s
Extra | Recovery of all triples for EPO patents took 37.45263338088989s
Performance | Total latancy measurement for EPO patents took 0.8599138259887695s
Amount of data | Number of triples check for EPO patents took 57.05630612373352s
Versatility | Languages check for EPO patents took 120.1043348312378s
Interpretability | Number of blank nodes check for EPO patents took 90.23268961906433s
Interpretability | RDF structures check for EPO patents took 0.22832536697387695s
Versatility | Serialization formats check for EPO patents took 0.20446538925170898s
Availability | RDF dump link check for EPO patents took 0.17591357231140137s
License | MR license check for EPO patents took 0.19372987747192383s
License | HR license check for EPO patents took 90.16265726089478s
Amount of data | Number of property check for EPO patents took 0.18604660034179688s
Understandability | Number of label check for EPO patents took 90.16517901420593s
Understandability | URI regex check for EPO patents took 0.44954633712768555s
Understandability | Vocabs check for EPO patents took 0.22216105461120605s
Verifiability | Authors check for EPO patents took 0.23159098625183105s
Verifiability | Publishers check for EPO patents took 0.20989179611206055s
Performance | Throughput check for EPO patents took 10.752284049987793s
Amount of data | Check the number of entities for EPO patents took 7.033348083496094e-05s
Verifiability | Contribs. check for EPO patents took 0.14467930793762207s
Interlinking | sameAs chians check for EPO patents took 0.15558815002441406s
Interlinking | skos check for EPO patents took 0.26598572731018066s
Interlinking | skos check for EPO patents took 0.17987561225891113s
Timeliness | dataset update frequency check for EPO patents took 0.16935467720031738s
Currency | Creation date check for EPO patents took 0.46035027503967285s
Currency | Modification date check for EPO patents took 0.36992788314819336s
Rep.Conc. | URIs length for EPO patents took 157.49299120903015s
Interoperability | New vocabularies check for EPO patents took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.16117048263549805s
Accuracy | Check Empty annotation labels for EPO patents took 18.986311435699463s
Accuracy | Check White space in annotation for EPO patents took 2.9762628078460693s
Accuracy | Check Datatype consistency for EPO patents took 4.871020078659058s
Consistency | Disjoint class check for EPO patents took 0.1916491985321045s
Consistency | Check Misplaced properties for EPO patents took 120.26583504676819s
Consistency | Check Ontology hijacking for EPO patents took 23.1957426071167s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.6027576923370361s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.47556018829346s
Conciseness | Check Extensional conciseness for EPO patents took 2.8250598907470703s
Conciseness | Check Intensional conciseness for EPO patents took 0.3351781368255615s
Security | Sign check for EPO patents took 0.2192211151123047s
Availability | Check URIs Dereferenciability for EPO patents took 1.2530128955841064s
Completeness | Calculation of interlinking completeness for EPO patents took 1.1661908626556396s
Reputation | Calculation of the PageRank for EPO patents took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.430511474609375e-06s
Believability | Calculation of trust value for EPO patents took 8.344650268554688e-06s
INFO | --- Analysis for European_Patent_Information took 1273.6209754943848s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.5299530029296875e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.7118213176727295s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.0517578125e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for europeana-lod took 6.0315101146698s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.482269287109375e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.3331565856933594s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.512901306152344e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 1.7881393432617188e-05s
INFO | --- Analysis for europeana-lod-v1 took 8.015337228775024s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.044432878494262695s
Availability | VoID file availability check for Europeana SPARQL took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.7183964252471924s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.021297931671142578s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0010023117065429688s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 6.389617919921875e-05s
Believability | Calculation of trust value for Europeana SPARQL took 7.867813110351562e-06s
INFO | --- Analysis for europeana-sparql took 6.04818320274353s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07796382904052734s
Availability | VoID file availability check for EuroSentiment took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.3098917007446289s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020263671875s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.6716461181640625e-05s
Believability | Calculation of trust value for EuroSentiment took 5.245208740234375e-06s
INFO | --- Analysis for eurosentiment took 3.3658225536346436s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.220008850097656e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0007562637329101562s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.2733631134033203s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.797645568847656e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.7220458984375e-06s
INFO | --- Analysis for eurostat-rdf took 12.228500366210938s
Availability | SPARQL endpoint availability check for EuroVoc took 0.35942792892456055s
Availability | VoID file availability check for EuroVoc took 0.000606536865234375s
Extra | Recovery of all triples for EuroVoc took 178.82291865348816s
Performance | Total latancy measurement for EuroVoc took 0.6632511615753174s
Amount of data | Number of triples check for EuroVoc took 0.7035014629364014s
Interoperability | New terms check for EuroVoc took 12.354318618774414s
Versatility | Languages check for EuroVoc took 300.0863380432129s
Interpretability | Number of blank nodes check for EuroVoc took 2.7460269927978516s
Security | Check HTTPS for EuroVoc took 0.39228343963623047s
Interpretability | RDF structures check for EuroVoc took 0.6174094676971436s
Versatility | Serialization formats check for EuroVoc took 3.516071081161499s
Availability | RDF dump link check for EuroVoc took 0.3037738800048828s
License | MR license check for EuroVoc took 0.30342769622802734s
License | HR license check for EuroVoc took 300.0066554546356s
Amount of data | Number of property check for EuroVoc took 0.17402386665344238s
Understandability | Number of label check for EuroVoc took 1.4526889324188232s
Understandability | URI regex check for EuroVoc took 0.27547359466552734s
Understandability | Vocabs check for EuroVoc took 0.12005376815795898s
Verifiability | Authors check for EuroVoc took 0.24195027351379395s
Verifiability | Publishers check for EuroVoc took 0.16283369064331055s
Performance | Throughput check for EuroVoc took 10.611621379852295s
Amount of data | Check the number of entities for EuroVoc took 0.00010991096496582031s
Verifiability | Contribs. check for EuroVoc took 0.24467897415161133s
Interlinking | sameAs chians check for EuroVoc took 0.9865660667419434s
Interlinking | skos check for EuroVoc took 0.44811534881591797s
Interlinking | skos check for EuroVoc took 0.4102060794830322s
Timeliness | dataset update frequency check for EuroVoc took 0.27222251892089844s
Currency | Creation date check for EuroVoc took 0.48398709297180176s
Currency | Modification date check for EuroVoc took 0.17975997924804688s
Rep.Conc. | URIs length for EuroVoc took 160.63020420074463s
Interoperability | New vocabularies check for EuroVoc took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.15386438369750977s
Accuracy | Check Functional Property for EuroVoc took 0.19266963005065918s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.15625429153442383s
Accuracy | Check Empty annotation labels for EuroVoc took 35.819058418273926s
Accuracy | Check White space in annotation for EuroVoc took 3.288654327392578s
Accuracy | Check Datatype consistency for EuroVoc took 2.663630723953247s
Consistency | Disjoint class check for EuroVoc took 0.2102975845336914s
Consistency | Check Misplaced properties for EuroVoc took 53.99383044242859s
Consistency | Misplaced classes for EuroVoc took 8.318857431411743s
Consistency | Check Ontology hijacking for EuroVoc took 24.26570439338684s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.685426950454712s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 54.776244163513184s
Conciseness | Check Extensional conciseness for EuroVoc took 2.9793057441711426s
Conciseness | Check Intensional conciseness for EuroVoc took 0.5143110752105713s
Security | Sign check for EuroVoc took 0.1189572811126709s
Availability | Check URIs Dereferenciability for EuroVoc took 9.083503484725952s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.1264159679412842s
Reputation | Calculation of the PageRank for EuroVoc took 0.021038055419921875s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.9073486328125e-06s
Believability | Calculation of trust value for EuroVoc took 7.3909759521484375e-06s
INFO | --- Analysis for eurovoc took 14640.647419929504s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 6.67572021484375e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.00034618377685546875s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.7681031227111816s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020882368087768555s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.124641418457031e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 1.1920928955078125e-05s
INFO | --- Analysis for eurovoc-in-skos took 4.006123065948486s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.673004150390625e-05s
Availability | VoID file availability check for European Television Heritage took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.7196135520935059s
Reputation | Calculation of the PageRank for European Television Heritage took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.8371810913085938e-05s
Believability | Calculation of trust value for European Television Heritage took 7.62939453125e-06s
INFO | --- Analysis for euscreen took 3.852119207382202s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.267692565917969e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2993605136871338s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.020275354385375977s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.57763671875e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 5.4836273193359375e-06s
INFO | --- Analysis for euskadi-farmacias took 7.250199317932129s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7758278846740723s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.27088332176208496s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020144224166870117s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 2.9087066650390625e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 8.106231689453125e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.895558595657349s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.33471131324768066s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0003638267517089844s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2744133472442627s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.021120309829711914s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 8.058547973632812e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 7.62939453125e-06s
INFO | --- Analysis for eutc-productions took 7.157547950744629s
Availability | SPARQL endpoint availability check for EventMedia took 0.3693830966949463s
Availability | VoID file availability check for EventMedia took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for EventMedia took 0.29958128929138184s
Reputation | Calculation of the PageRank for EventMedia took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00011181831359863281s
Believability | Calculation of trust value for EventMedia took 6.4373016357421875e-06s
INFO | --- Analysis for event-media took 9.99842619895935s
Availability | SPARQL endpoint availability check for EventKG took 4.220008850097656e-05s
Availability | VoID file availability check for EventKG took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for EventKG took 0.2609519958496094s
Reputation | Calculation of the PageRank for EventKG took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for EventKG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EventKG took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.535385131835938e-05s
Believability | Calculation of trust value for EventKG took 6.9141387939453125e-06s
INFO | --- Analysis for eventkg took 5.25787353515625s
Availability | SPARQL endpoint availability check for Eventseer took 1.073096752166748s
Availability | VoID file availability check for Eventseer took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2846529483795166s
Reputation | Calculation of the PageRank for Eventseer took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.887580871582031e-05s
Believability | Calculation of trust value for Eventseer took 7.867813110351562e-06s
INFO | --- Analysis for eventseer took 3.5620079040527344s
Availability | SPARQL endpoint availability check for Face Link took 4.2438507080078125e-05s
Availability | VoID file availability check for Face Link took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Face Link took 0.24218058586120605s
Reputation | Calculation of the PageRank for Face Link took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for Face Link took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Face Link took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.3855438232421875e-05s
Believability | Calculation of trust value for Face Link took 6.9141387939453125e-06s
INFO | --- Analysis for Face_Link took 2.3836376667022705s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.220008850097656e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.2750740051269531s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 2.9087066650390625e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 7.867813110351562e-06s
INFO | --- Analysis for facebook-lids took 3.0617363452911377s
Availability | SPARQL endpoint availability check for Fact Forge took 4.100799560546875e-05s
Availability | VoID file availability check for Fact Forge took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.23595905303955078s
Reputation | Calculation of the PageRank for Fact Forge took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Fact Forge took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 2.9325485229492188e-05s
Believability | Calculation of trust value for Fact Forge took 7.3909759521484375e-06s
INFO | --- Analysis for fact-forge took 2.891846179962158s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5956315994262695s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0002694129943847656s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 124.29551649093628s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9575650691986084s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.159323453903198s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.06766939163208s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2543377876282s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.252673387527466s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2687690258026123s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 12.222114324569702s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22500848770141602s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4183335304260254s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2411365509033s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.31669163703918457s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.5502102375030518s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6426894664764404s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.29932737350463867s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20175409317016602s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2574775218963623s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.32507848739624s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.818771362304688e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19852614402770996s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1960752010345459s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4381265640258789s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4440474510192871s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.663583755493164s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.47365307807922363s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22263193130493164s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 151.78712129592896s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2147514820098877s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3423185348510742s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.33644866943359375s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 37.62128233909607s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6978628635406494s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6267244815826416s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1980431079864502s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 83.37085175514221s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.403557538986206s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 36.97945308685303s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3640937805175781s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 80.99593305587769s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.751492977142334s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5234506130218506s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.7915537357330322s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.663888931274414s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3446905612945557s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020854473114013672s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.030632019042969e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for FADN_(2019) took 2260.6918761730194s
Availability | SPARQL endpoint availability check for FAMEData took 4.315376281738281e-05s
Availability | VoID file availability check for FAMEData took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for FAMEData took 0.7143337726593018s
Reputation | Calculation of the PageRank for FAMEData took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.1948089599609375e-05s
Believability | Calculation of trust value for FAMEData took 8.106231689453125e-06s
INFO | --- Analysis for famedata took 8.975674390792847s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.38690185546875e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.2582824230194092s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.03003835678100586s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00011515617370605469s
Believability | Calculation of trust value for FAO geopolitical ontology took 4.291534423828125e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 13.158684492111206s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.739732027053833s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.2578120231628418s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00011849403381347656s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 4.291534423828125e-06s
INFO | --- Analysis for fao-linked-data took 3.684779167175293s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.267692565917969e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.2476482391357422s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.02031707763671875s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.123283386230469e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 6.198883056640625e-06s
INFO | --- Analysis for FAO_species took 2.357820510864258s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.458316564559937s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2582080364227295s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.482269287109375e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 7.867813110351562e-06s
INFO | --- Analysis for farmbio-chembl took 64.95460367202759s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.076957702636719e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.27248525619506836s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.02078866958618164s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.24249267578125e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 7.3909759521484375e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 3.432757616043091s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.00543212890625e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.0003123283386230469s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.7694282531738281s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 7.62939453125e-06s
INFO | --- Analysis for farolapp-dataset took 3.7963826656341553s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.2438507080078125e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.26993322372436523s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 3.0040740966796875e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 7.152557373046875e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 3.3533942699432373s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.601478576660156e-05s
Availability | VoID file availability check for I4.0-Onto took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.2593197822570801s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.266334533691406e-05s
Believability | Calculation of trust value for I4.0-Onto took 7.867813110351562e-06s
INFO | --- Analysis for fatimazahra took 2.3724215030670166s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.28337860107421875s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.0517578125e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 7.152557373046875e-06s
INFO | --- Analysis for federal-economic-rdf took 2.9716432094573975s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.220008850097656e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.2660808563232422s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.020985126495361328s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 2.86102294921875e-05s
Believability | Calculation of trust value for Feed Wrapper took 8.106231689453125e-06s
INFO | --- Analysis for feedwrapper-lids took 2.886153221130371s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.220008850097656e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.2634449005126953s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.0994415283203125e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.1682510375976562e-05s
INFO | --- Analysis for FHIR_STU3 took 2.7008910179138184s
Availability | SPARQL endpoint availability check for FiESTA took 4.792213439941406e-05s
Availability | VoID file availability check for FiESTA took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for FiESTA took 0.2673647403717041s
Reputation | Calculation of the PageRank for FiESTA took 0.020249128341674805s
Interlinking | Calculation of Degree of Connection for FiESTA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.981590270996094e-05s
Believability | Calculation of trust value for FiESTA took 3.552436828613281e-05s
INFO | --- Analysis for fiesta took 12.625780820846558s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.3392181396484375e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.25816941261291504s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.765655517578125e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 6.67572021484375e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.3753998279571533s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.458427429199219e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.24447965621948242s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.914138793945312e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.4836273193359375e-06s
INFO | --- Analysis for finnish-municipalities took 4.177865266799927s
Availability | SPARQL endpoint availability check for firmao took 4.029273986816406e-05s
Availability | VoID file availability check for firmao took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for firmao took 0.2677476406097412s
Reputation | Calculation of the PageRank for firmao took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for firmao took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for firmao took 2.9087066650390625e-05s
Believability | Calculation of trust value for firmao took 7.3909759521484375e-06s
INFO | --- Analysis for firmao took 2.905660390853882s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.26335883140563965s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 2.9325485229492188e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.9286093711853027s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.21914196014404297s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0002532005310058594s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 128.1044454574585s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.9633238315582275s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 7.5602452754974365s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 13.077212810516357s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.17401599884033s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.6175968647003174s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.2554605007171631s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 10.823341846466064s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.26360559463500977s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.36600804328918457s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.1682517528534s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.18819761276245117s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.5684170722961426s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.6832461357116699s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.42984676361083984s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.20110559463500977s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.26336145401000977s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.304728746414185s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.271766662597656e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.22984671592712402s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.20544958114624023s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4601459503173828s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4661862850189209s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 5.782024383544922s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.519242525100708s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.20283770561218262s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 165.57461881637573s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.2163693904876709s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.3813915252685547s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.27916836738586426s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 38.44038152694702s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.6728761196136475s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.588486671447754s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.18182992935180664s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 83.4346981048584s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.472755432128906s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 43.41894340515137s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.3985278606414795s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 84.57659196853638s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.7693469524383545s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.5299534797668457s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.7852756977081299s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 10.103770732879639s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 1.4843132495880127s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.021292924880981445s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 2281.4437425136566s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.863739013671875e-05s
Availability | VoID file availability check for Fishes of Texas took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.27904415130615234s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.021013259887695312s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 0.00011658668518066406s
Believability | Calculation of trust value for Fishes of Texas took 6.9141387939453125e-06s
INFO | --- Analysis for fishes-of-texas took 4.6919989585876465s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.2438507080078125e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.2545650005340576s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 0.0001270771026611328s
Believability | Calculation of trust value for flickr? wrappr took 7.152557373046875e-06s
INFO | --- Analysis for flickr-wrappr took 4.193662881851196s
Availability | SPARQL endpoint availability check for flickr.person took 4.100799560546875e-05s
Availability | VoID file availability check for flickr.person took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for flickr.person took 0.2697257995605469s
Reputation | Calculation of the PageRank for flickr.person took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for flickr.person took 2.765655517578125e-05s
Believability | Calculation of trust value for flickr.person took 7.152557373046875e-06s
INFO | --- Analysis for flickr_person took 3.424933910369873s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.5299530029296875e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.2711186408996582s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.02071547508239746s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.123283386230469e-05s
Believability | Calculation of trust value for flickr.videoobject took 8.106231689453125e-06s
INFO | --- Analysis for flickr_videoobject took 2.8613927364349365s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.315376281738281e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.27942538261413574s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02027153968811035s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 2.9087066650390625e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.0013580322265625e-05s
INFO | --- Analysis for FLUS took 9.504420518875122s
Availability | SPARQL endpoint availability check for Fly-TED took 4.0531158447265625e-05s
Availability | VoID file availability check for Fly-TED took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.24852848052978516s
Reputation | Calculation of the PageRank for Fly-TED took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 2.86102294921875e-05s
Believability | Calculation of trust value for Fly-TED took 6.9141387939453125e-06s
INFO | --- Analysis for fly-ted took 3.303165912628174s
Availability | SPARQL endpoint availability check for FlyAtlas took 4.291534423828125e-05s
Availability | VoID file availability check for FlyAtlas took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.27189016342163086s
Reputation | Calculation of the PageRank for FlyAtlas took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 2.7179718017578125e-05s
Believability | Calculation of trust value for FlyAtlas took 8.106231689453125e-06s
INFO | --- Analysis for flyatlas took 3.13356614112854s
Availability | SPARQL endpoint availability check for Flybase took 1.8424270153045654s
Availability | VoID file availability check for Flybase took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Flybase took 0.2719144821166992s
Reputation | Calculation of the PageRank for Flybase took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for Flybase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0008471012115478516s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.504753112792969e-05s
Believability | Calculation of trust value for Flybase took 6.9141387939453125e-06s
INFO | --- Analysis for flybase took 10.249206304550171s
Availability | SPARQL endpoint availability check for Flyted took 1.3780925273895264s
Availability | VoID file availability check for Flyted took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Flyted took 0.269578218460083s
Reputation | Calculation of the PageRank for Flyted took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Flyted took 2.8848648071289062e-05s
Believability | Calculation of trust value for Flyted took 7.152557373046875e-06s
INFO | --- Analysis for flyted took 11.396576642990112s
Availability | SPARQL endpoint availability check for Foodista took 1.1447257995605469s
Availability | VoID file availability check for Foodista took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Foodista took 0.2590165138244629s
Reputation | Calculation of the PageRank for Foodista took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Foodista took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.361701965332031e-05s
Believability | Calculation of trust value for Foodista took 7.3909759521484375e-06s
INFO | --- Analysis for foodista took 12.27430772781372s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17484474182128906s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00037360191345214844s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2482624053955078s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020401716232299805s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.414817810058594e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.62939453125e-06s
INFO | --- Analysis for foodpedia took 2.6035475730895996s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.1961669921875e-05s
Availability | VoID file availability check for FORGE Course information took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.2668888568878174s
Reputation | Calculation of the PageRank for FORGE Course information took 0.020344972610473633s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0009453296661376953s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.457069396972656e-05s
Believability | Calculation of trust value for FORGE Course information took 1.1920928955078125e-05s
INFO | --- Analysis for forge-course-information took 2.9355123043060303s
Availability | SPARQL endpoint availability check for FrameBase schema took 8.845329284667969e-05s
Availability | VoID file availability check for FrameBase schema took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.25942373275756836s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.506111145019531e-05s
Believability | Calculation of trust value for FrameBase schema took 6.9141387939453125e-06s
INFO | --- Analysis for framebase-schema took 2.985581159591675s
Availability | SPARQL endpoint availability check for FrameNet took 4.172325134277344e-05s
Availability | VoID file availability check for FrameNet took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for FrameNet took 0.2714865207672119s
Reputation | Calculation of the PageRank for FrameNet took 0.020449399948120117s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for FrameNet took 2.9087066650390625e-05s
Believability | Calculation of trust value for FrameNet took 7.152557373046875e-06s
INFO | --- Analysis for framenet took 2.896440029144287s
Availability | SPARQL endpoint availability check for Framester took 4.38690185546875e-05s
Availability | VoID file availability check for Framester took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for Framester took 0.2778346538543701s
Reputation | Calculation of the PageRank for Framester took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for Framester took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Framester took 7.748603820800781e-05s
Believability | Calculation of trust value for Framester took 7.152557373046875e-06s
INFO | --- Analysis for framester took 3.4476819038391113s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.1720876693725586s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0003540515899658203s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2827482223510742s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.606910705566406e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for frb-linked-data took 2.608961343765259s
Availability | SPARQL endpoint availability check for Freebase took 4.291534423828125e-05s
Availability | VoID file availability check for Freebase took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Freebase took 0.2524597644805908s
Reputation | Calculation of the PageRank for Freebase took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.0002942085266113281s
Believability | Calculation of trust value for Freebase took 7.62939453125e-06s
INFO | --- Analysis for freebase took 4.461838006973267s
Availability | SPARQL endpoint availability check for Freeyork took 4.291534423828125e-05s
Availability | VoID file availability check for Freeyork took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Freeyork took 0.273608922958374s
Reputation | Calculation of the PageRank for Freeyork took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010204315185546875s
Believability | Calculation of trust value for Freeyork took 7.152557373046875e-06s
INFO | --- Analysis for freeyork-org took 2.933976650238037s
Availability | SPARQL endpoint availability check for French School Program took 4.291534423828125e-05s
Availability | VoID file availability check for French School Program took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for French School Program took 0.2501380443572998s
Reputation | Calculation of the PageRank for French School Program took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for French School Program took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.170967102050781e-05s
Believability | Calculation of trust value for French School Program took 7.62939453125e-06s
INFO | --- Analysis for french-school-program took 2.885483741760254s
Availability | SPARQL endpoint availability check for French School System took 4.172325134277344e-05s
Availability | VoID file availability check for French School System took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for French School System took 0.26184582710266113s
Reputation | Calculation of the PageRank for French School System took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for French School System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for French School System took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for French School System took 2.956390380859375e-05s
Believability | Calculation of trust value for French School System took 7.3909759521484375e-06s
INFO | --- Analysis for french-school-system took 2.927642583847046s
Availability | SPARQL endpoint availability check for French TimeBank took 4.1484832763671875e-05s
Availability | VoID file availability check for French TimeBank took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.2587251663208008s
Reputation | Calculation of the PageRank for French TimeBank took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.075599670410156e-05s
Believability | Calculation of trust value for French TimeBank took 6.67572021484375e-06s
INFO | --- Analysis for french-timebank took 2.921109199523926s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7912113666534424s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.2802596092224121s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02031683921813965s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.557868957519531e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.491440057754517s
Availability | SPARQL endpoint availability check for DailyMed took 0.720670223236084s
Availability | VoID file availability check for DailyMed took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2822227478027344s
Reputation | Calculation of the PageRank for DailyMed took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.918212890625e-05s
Believability | Calculation of trust value for DailyMed took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.681450366973877s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7531087398529053s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.24058175086975098s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.678436279296875e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.421849489212036s
Availability | SPARQL endpoint availability check for Diseasome took 0.7235441207885742s
Availability | VoID file availability check for Diseasome took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Diseasome took 0.2557363510131836s
Reputation | Calculation of the PageRank for Diseasome took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for Diseasome took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diseasome took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010919570922851562s
Believability | Calculation of trust value for Diseasome took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.65273904800415s
Availability | SPARQL endpoint availability check for DrugBank took 0.7444775104522705s
Availability | VoID file availability check for DrugBank took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2630345821380615s
Reputation | Calculation of the PageRank for DrugBank took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.0001201629638671875s
Believability | Calculation of trust value for DrugBank took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.705169916152954s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6980938911437988s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2451467514038086s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020269393920898438s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 5.2928924560546875e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.289558410644531s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6947293281555176s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2906370162963867s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020303726196289062s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.510185241699219e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.408691883087158s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.6936633586883545s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.25985240936279297s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.271766662597656e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-eures took 4.343567848205566s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.7442173957824707s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.24012470245361328s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 4.1484832763671875e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.512901306152344e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 4.76837158203125e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.012091398239136s
Availability | SPARQL endpoint availability check for MediCare took 0.7099316120147705s
Availability | VoID file availability check for MediCare took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for MediCare took 0.28368043899536133s
Reputation | Calculation of the PageRank for MediCare took 0.020926713943481445s
Interlinking | Calculation of Degree of Connection for MediCare took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.267692565917969e-05s
Believability | Calculation of trust value for MediCare took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-medicare took 5.188617706298828s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7317585945129395s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.28215503692626953s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 8.0108642578125e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 6.4373016357421875e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.519272327423096s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7184717655181885s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.26703476905822754s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020203113555908203s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.131431579589844e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-sider took 4.968947887420654s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7081513404846191s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.29763245582580566s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.891654968261719e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.534058094024658s
Availability | SPARQL endpoint availability check for fvdb took 5.4836273193359375e-05s
Availability | VoID file availability check for fvdb took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for fvdb took 0.2662644386291504s
Reputation | Calculation of the PageRank for fvdb took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for fvdb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.0040740966796875e-05s
Believability | Calculation of trust value for fvdb took 6.67572021484375e-06s
INFO | --- Analysis for fv took 12.378896236419678s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.2438507080078125e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.25223469734191895s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.021331071853637695s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0009214878082275391s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.6716461181640625e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 7.62939453125e-06s
INFO | --- Analysis for GACS took 3.0262813568115234s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.1961669921875e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.264693021774292s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 2.9802322387695312e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 1.1682510375976562e-05s
INFO | --- Analysis for galen_from_co-odeorg took 2.899925708770752s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.3392181396484375e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.2618074417114258s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.100799560546875e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.3113021850585938e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 4.965914964675903s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.315376281738281e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.24486947059631348s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0010306835174560547s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00012040138244628906s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for garnicaplywood took 3.7094411849975586s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.291534423828125e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.2605612277984619s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02072596549987793s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.179115295410156e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.62939453125e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.412923097610474s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.35122203826904297s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.28539443016052246s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.34600830078125e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for gemet took 5.0743207931518555s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.2438507080078125e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.29497194290161133s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020597219467163086s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.504753112792969e-05s
Believability | Calculation of trust value for gemet-annotated took 6.9141387939453125e-06s
INFO | --- Analysis for gemet-annotated took 2.8936808109283447s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7910540103912354s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.26207733154296875s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.9577484130859375e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 7.867813110351562e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.162747621536255s
Availability | SPARQL endpoint availability check for Super Ontology took 0.755441427230835s
Availability | VoID file availability check for Super Ontology took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2585179805755615s
Reputation | Calculation of the PageRank for Super Ontology took 0.0201416015625s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Super Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 4.382816314697266s
Availability | SPARQL endpoint availability check for geo.place took 5.6743621826171875e-05s
Availability | VoID file availability check for geo.place took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for geo.place took 0.2458341121673584s
Reputation | Calculation of the PageRank for geo.place took 0.020333528518676758s
Interlinking | Calculation of Degree of Connection for geo.place took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for geo.place took 2.9087066650390625e-05s
Believability | Calculation of trust value for geo.place took 7.62939453125e-06s
INFO | --- Analysis for geo_place took 2.961646556854248s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.3392181396484375e-05s
Availability | VoID file availability check for Geographic detector model took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.27121758460998535s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.0994415283203125e-05s
Believability | Calculation of trust value for Geographic detector model took 7.152557373046875e-06s
INFO | --- Analysis for GeoDetector took 11.416469097137451s
Availability | SPARQL endpoint availability check for geodomainwn took 4.363059997558594e-05s
Availability | VoID file availability check for geodomainwn took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.2406444549560547s
Reputation | Calculation of the PageRank for geodomainwn took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.673004150390625e-05s
Believability | Calculation of trust value for geodomainwn took 8.106231689453125e-06s
INFO | --- Analysis for geodomainwn took 6.622835159301758s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.315376281738281e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.29425621032714844s
Reputation | Calculation of the PageRank for GeoEcuador took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0008604526519775391s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 8.58306884765625e-05s
Believability | Calculation of trust value for GeoEcuador took 7.62939453125e-06s
INFO | --- Analysis for geoecuador took 12.457684993743896s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.0719070434570312s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.3683469295501709s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.021274566650390625s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.62939453125e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.1920928955078125e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.66135931015015s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 7.200241088867188e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.2769603729248047s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020635604858398438s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 2.9325485229492188e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 8.106231689453125e-06s
INFO | --- Analysis for geographic-openuplabs took 2.894666910171509s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.571256160736084s
Availability | VoID file availability check for GeoLinkedData took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.2739112377166748s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020815372467041016s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 0.00010919570922851562s
Believability | Calculation of trust value for GeoLinkedData took 5.0067901611328125e-06s
INFO | --- Analysis for geolinkeddata took 4.042200803756714s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.2430706024169922s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0012559890747070312s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 12.185214519500732s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.3778700828552246s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.1595470905303955s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.4498200416564941s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.1979207992553711s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.1683034896850586s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.16902899742126465s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.08657217025756836s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.08607006072998047s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.0757288932800293s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.0927741527557373s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 2.018082618713379s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.09373068809509277s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.09252238273620605s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.12994909286499023s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.09259200096130371s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.07107090950012207s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10082817077636719s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.344361066818237s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 7.152557373046875e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06880497932434082s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06107521057128906s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.09294509887695312s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06167483329772949s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06929302215576172s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1579878330230713s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1863727569580078s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.5556607246398926s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 4.7227113246917725s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08635139465332031s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06752228736877441s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.05980277061462402s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.3342933654785156s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007257223129272461s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.22838759422302246s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06845784187316895s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.20444560050964355s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5236945152282715s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.2555954456329346s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.5194635391235352s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.6888718605041504s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17911982536315918s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07598280906677246s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 0.9981918334960938s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.2835700511932373s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 9.059906005859375e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 3.0431439876556396s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 123.18152165412903s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 5.435943603515625e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.28726840019226074s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004677772521972656s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.62939453125e-06s
INFO | --- Analysis for geonames-semantic-web took 3.26151967048645s
Availability | SPARQL endpoint availability check for Geospatial World  took 8.177757263183594e-05s
Availability | VoID file availability check for Geospatial World  took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.2663390636444092s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020219802856445312s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010585784912109375s
Believability | Calculation of trust value for Geospatial World  took 7.152557373046875e-06s
INFO | --- Analysis for geospatialworld-net took 2.927088737487793s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.6506505012512207s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.24578404426574707s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013709068298339844s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for geospecies took 6.255505084991455s
Availability | SPARQL endpoint availability check for GeoWordNet took 7.390975952148438e-05s
Availability | VoID file availability check for GeoWordNet took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.26965951919555664s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.9114227294921875e-05s
Believability | Calculation of trust value for GeoWordNet took 7.152557373046875e-06s
INFO | --- Analysis for geowordnet took 7.244525194168091s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.1799631118774414s
Availability | VoID file availability check for German labor law thesaurus took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.25696563720703125s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.130073547363281e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.6220791339874268s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.458427429199219e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.2771615982055664s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020558595657348633s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0010325908660888672s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.887580871582031e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 6.9141387939453125e-06s
INFO | --- Analysis for germlex took 2.8233449459075928s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.5005519390106201s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007104873657226562s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2722320556640625s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.821487426757812e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 7.3909759521484375e-06s
INFO | --- Analysis for gesis-thesoz took 5.827035903930664s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.8127694129943848s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.27288269996643066s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.867813110351562e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for getty-aat took 24.737648725509644s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 2.4269611835479736s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2548196315765381s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020413875579833984s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.817413330078125e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 7.3909759521484375e-06s
INFO | --- Analysis for getty-tgn took 23.251256227493286s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.352783203125s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.26500391960144043s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02068185806274414s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.170967102050781e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 1.0251998901367188e-05s
INFO | --- Analysis for gipuzkoademografia took 2.902034282684326s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.267692565917969e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.2728571891784668s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0009093284606933594s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.3855438232421875e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.0967254638671875e-05s
INFO | --- Analysis for glastonbury-2011 took 5.709870338439941s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.506111145019531e-05s
Availability | VoID file availability check for Global Change Information System took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.2554295063018799s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.0517578125e-05s
Believability | Calculation of trust value for Global Change Information System took 7.3909759521484375e-06s
INFO | --- Analysis for global-change-information-system took 2.942289352416992s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.8160552978515625e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.29022693634033203s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.744529724121094e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.9141387939453125e-06s
INFO | --- Analysis for global-hunger-index-2011 took 3.112811326980591s
Availability | SPARQL endpoint availability check for Glottolog took 4.267692565917969e-05s
Availability | VoID file availability check for Glottolog took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2635641098022461s
Reputation | Calculation of the PageRank for Glottolog took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Glottolog took 4.863739013671875e-05s
Believability | Calculation of trust value for Glottolog took 7.3909759521484375e-06s
INFO | --- Analysis for glottolog took 6.464328289031982s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.38690185546875e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2581822872161865s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010228157043457031s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 7.3909759521484375e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 9.498594045639038s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.076957702636719e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.25006890296936035s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.7894973754882812e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 7.152557373046875e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.8983285427093506s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.291534423828125e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.2707021236419678s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 2.765655517578125e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 8.106231689453125e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.9207377433776855s
Availability | SPARQL endpoint availability check for 1121 took 6.127357482910156e-05s
Availability | VoID file availability check for 1121 took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for 1121 took 0.2667384147644043s
Reputation | Calculation of the PageRank for 1121 took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for 1121 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 1121 took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.5762786865234375e-05s
Believability | Calculation of trust value for 1121 took 1.239776611328125e-05s
INFO | --- Analysis for God_ took 2.7927138805389404s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.3392181396484375e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2594294548034668s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.021012306213378906s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.221366882324219e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 7.152557373046875e-06s
INFO | --- Analysis for gold took 4.0497658252716064s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.553794860839844e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.28339505195617676s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.890296936035156e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 6.9141387939453125e-06s
INFO | --- Analysis for googleart-wrapper took 2.7773830890655518s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.11368060111999512s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2658703327178955s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.409385681152344e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 7.152557373046875e-06s
INFO | --- Analysis for govagribus-denmark took 34.52520537376404s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.428224563598633s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.2697610855102539s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.021131515502929688s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 9.107589721679688e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 23.953229665756226s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.6914281845092773s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.25718188285827637s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.702278137207031e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 4.291534423828125e-06s
INFO | --- Analysis for govtrack took 10.35406756401062s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 6.961822509765625e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.25838565826416016s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0009062290191650391s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.890296936035156e-05s
Believability | Calculation of trust value for greek-administrative-geography took 8.58306884765625e-06s
INFO | --- Analysis for greek-administrative-geography took 2.5790367126464844s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.3254578113555908s
Availability | VoID file availability check for Greek Wordnet took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.24584364891052246s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020811796188354492s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.1484832763671875e-05s
Believability | Calculation of trust value for Greek Wordnet took 7.62939453125e-06s
INFO | --- Analysis for greek-wordnet took 2.7208542823791504s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5671281814575195s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.28516316413879395s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.239776611328125e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 1.1682510375976562e-05s
INFO | --- Analysis for greek_prisons_releases took 4.843659400939941s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.9033839702606201s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2841486930847168s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.58306884765625e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.9141387939453125e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.633166790008545s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.5299530029296875e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0007545948028564453s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.2807579040527344s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.0001010894775390625s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 6.901219606399536s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.8696210384368896s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2736177444458008s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.57763671875e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 7.62939453125e-06s
INFO | --- Analysis for grrp took 4.389573097229004s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.1255121231079102s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0003781318664550781s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.27777957916259766s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 8.153915405273438e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.245208740234375e-06s
INFO | --- Analysis for grrt took 3.5915675163269043s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1272192001342773s
Availability | VoID file availability check for Geological Timescale took 0.0007092952728271484s
Extra | Recovery of all triples for Geological Timescale took 2.4512338638305664s
Performance | Total latancy measurement for Geological Timescale took 3.6179659366607666s
Amount of data | Number of triples check for Geological Timescale took 0.9655985832214355s
Interoperability | New terms check for Geological Timescale took 1.6937124729156494s
Versatility | Languages check for Geological Timescale took 1.0875306129455566s
Interpretability | Number of blank nodes check for Geological Timescale took 1.9671437740325928s
Security | Check HTTPS for Geological Timescale took 1.8785686492919922s
Interpretability | RDF structures check for Geological Timescale took 0.40512609481811523s
Versatility | Serialization formats check for Geological Timescale took 0.9230842590332031s
Availability | RDF dump link check for Geological Timescale took 1.6527736186981201s
License | MR license check for Geological Timescale took 0.9171569347381592s
License | HR license check for Geological Timescale took 0.38964176177978516s
Amount of data | Number of property check for Geological Timescale took 0.9316444396972656s
Understandability | Number of label check for Geological Timescale took 0.4313814640045166s
Understandability | URI regex check for Geological Timescale took 0.770686149597168s
Understandability | Vocabs check for Geological Timescale took 0.3783855438232422s
Verifiability | Authors check for Geological Timescale took 0.40366148948669434s
Verifiability | Publishers check for Geological Timescale took 0.9552700519561768s
Performance | Throughput check for Geological Timescale took 12.5379056930542s
Amount of data | Check the number of entities for Geological Timescale took 0.02185201644897461s
Verifiability | Contribs. check for Geological Timescale took 0.9708702564239502s
Interlinking | sameAs chians check for Geological Timescale took 0.37460756301879883s
Interlinking | skos check for Geological Timescale took 0.8928701877593994s
Interlinking | skos check for Geological Timescale took 0.3876039981842041s
Timeliness | dataset update frequency check for Geological Timescale took 0.37843847274780273s
Currency | Creation date check for Geological Timescale took 0.8125960826873779s
Currency | Modification date check for Geological Timescale took 0.376201868057251s
Rep.Conc. | URIs length for Geological Timescale took 1.4477152824401855s
Interoperability | New vocabularies check for Geological Timescale took 9.020943641662598s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.9208414554595947s
Accuracy | Check Functional Property for Geological Timescale took 0.3875541687011719s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9331181049346924s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.3058767318725586s
Accuracy | Check White space in annotation for Geological Timescale took 0.01567387580871582s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07260918617248535s
Consistency | Disjoint class check for Geological Timescale took 0.4113593101501465s
Consistency | Check Misplaced properties for Geological Timescale took 0.8004915714263916s
Consistency | Misplaced classes for Geological Timescale took 0.9983706474304199s
Consistency | Check Ontology hijacking for Geological Timescale took 1.6919231414794922s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2694892883300781s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.2100276947021484s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05042457580566406s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.931755781173706s
Security | Sign check for Geological Timescale took 0.9575605392456055s
Availability | Check URIs Dereferenciability for Geological Timescale took 2.6652534008026123s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.26586198806762695s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 8.392333984375e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 7.072004318237305s
Believability | Calculation of trust value for Geological Timescale took 6.9141387939453125e-06s
INFO | --- Analysis for GTS took 113.53154063224792s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2663278579711914s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.218650817871094e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 7.62939453125e-06s
INFO | --- Analysis for GTS-ont took 2.664271593093872s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.291534423828125e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.2674252986907959s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 2.8371810913085938e-05s
Believability | Calculation of trust value for GUTSTOK  took 6.67572021484375e-06s
INFO | --- Analysis for Guillaume_Forget took 2.427370309829712s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.220008850097656e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.275604248046875s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020217418670654297s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.2479248046875e-05s
Believability | Calculation of trust value for Project Gutenberg took 7.152557373046875e-06s
INFO | --- Analysis for gutenberg took 28.34307026863098s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.2438507080078125e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.28362154960632324s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02022862434387207s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.4809112548828125e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.1205673217773438e-05s
INFO | --- Analysis for gwa-ili took 5.261627435684204s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.291534423828125e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.2726433277130127s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 2.8848648071289062e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 6.4373016357421875e-06s
INFO | --- Analysis for GWR took 14.251291990280151s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.220008850097656e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.2519979476928711s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.170967102050781e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 8.821487426757812e-06s
INFO | --- Analysis for HASM took 8.40164041519165s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.029273986816406e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.27588367462158203s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.337860107421875e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 7.3909759521484375e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.9507834911346436s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.040726900100708s
Availability | VoID file availability check for HealthCare Ontology took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.265519380569458s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 4.029273986816406e-05s
Believability | Calculation of trust value for HealthCare Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for HealthCare_Ontology took 5.771705150604248s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.267692565917969e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0003495216369628906s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.285999059677124s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.127357482910156e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 6.198883056640625e-06s
INFO | --- Analysis for heartfailure took 2.7872867584228516s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.76021933555603s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007760524749755859s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.38922119140625s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.291534423828125e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 6.9141387939453125e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 120.60780382156372s
Availability | SPARQL endpoint availability check for Hedatuz took 0.2696347236633301s
Availability | VoID file availability check for Hedatuz took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.2848842144012451s
Reputation | Calculation of the PageRank for Hedatuz took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.5299530029296875e-05s
Believability | Calculation of trust value for Hedatuz took 7.62939453125e-06s
INFO | --- Analysis for hedatuz took 2.9804253578186035s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.17133283615112305s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2749011516571045s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012874603271484375s
Believability | Calculation of trust value for Hellenic Fire Brigade took 4.5299530029296875e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.560359239578247s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.021768569946289062s
Availability | VoID file availability check for Hellenic Police took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.2516353130340576s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001323223114013672s
Believability | Calculation of trust value for Hellenic Police took 5.4836273193359375e-06s
INFO | --- Analysis for hellenic-police took 2.409229278564453s
Availability | SPARQL endpoint availability check for Hermos took 4.38690185546875e-05s
Availability | VoID file availability check for Hermos took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Hermos took 0.2540600299835205s
Reputation | Calculation of the PageRank for Hermos took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.0994415283203125e-05s
Believability | Calculation of trust value for Hermos took 7.152557373046875e-06s
INFO | --- Analysis for Hermos took 2.9802732467651367s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.696846008300781e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.26390671730041504s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.956390380859375e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 7.152557373046875e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.401707887649536s
Availability | SPARQL endpoint availability check for HITO took 0.4186739921569824s
Availability | VoID file availability check for HITO took 0.0006382465362548828s
Extra | Recovery of all triples for HITO took 3.2609705924987793s
Performance | Total latancy measurement for HITO took 1.010718584060669s
Amount of data | Number of triples check for HITO took 0.19634580612182617s
Interoperability | New terms check for HITO took 1.527076005935669s
Versatility | Languages check for HITO took 0.22183895111083984s
Interpretability | Number of blank nodes check for HITO took 0.19571638107299805s
Interpretability | RDF structures check for HITO took 0.19887185096740723s
Versatility | Serialization formats check for HITO took 0.18537688255310059s
Availability | RDF dump link check for HITO took 0.1839616298675537s
License | MR license check for HITO took 0.19592046737670898s
License | HR license check for HITO took 0.21046805381774902s
Amount of data | Number of property check for HITO took 0.20804262161254883s
Understandability | Number of label check for HITO took 0.19878721237182617s
Understandability | URI regex check for HITO took 0.3901031017303467s
Understandability | Vocabs check for HITO took 0.18495869636535645s
Verifiability | Authors check for HITO took 0.19750142097473145s
Verifiability | Publishers check for HITO took 0.18555068969726562s
Performance | Throughput check for HITO took 11.50439167022705s
Amount of data | Check the number of entities for HITO took 0.00010728836059570312s
Verifiability | Contribs. check for HITO took 0.19537687301635742s
Interlinking | sameAs chians check for HITO took 0.2062077522277832s
Interlinking | skos check for HITO took 0.1952970027923584s
Interlinking | skos check for HITO took 0.18367505073547363s
Timeliness | dataset update frequency check for HITO took 0.19722890853881836s
Currency | Creation date check for HITO took 0.38272857666015625s
Currency | Modification date check for HITO took 0.3816840648651123s
Rep.Conc. | URIs length for HITO took 1.1670520305633545s
Interoperability | New vocabularies check for HITO took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.19522571563720703s
Accuracy | Check Functional Property for HITO took 0.18606090545654297s
Accuracy | Check Inverse Functional Property for HITO took 0.19530296325683594s
Accuracy | Check Empty annotation labels for HITO took 0.5543968677520752s
Accuracy | Check White space in annotation for HITO took 0.013231515884399414s
Accuracy | Check Datatype consistency for HITO took 0.07537055015563965s
Consistency | Disjoint class check for HITO took 0.18435287475585938s
Consistency | Check Misplaced properties for HITO took 0.5328197479248047s
Consistency | Misplaced classes for HITO took 0.36730527877807617s
Consistency | Check Ontology hijacking for HITO took 1.7395057678222656s
Consistency | Check Invalid usage of undefined classes for HITO took 1.2561020851135254s
Consistency | Check Invalid usage of undefined properties for HITO took 1.5030391216278076s
Conciseness | Check Extensional conciseness for HITO took 0.05962777137756348s
Conciseness | Check Intensional conciseness for HITO took 0.18467307090759277s
Security | Sign check for HITO took 0.18482565879821777s
Availability | Check URIs Dereferenciability for HITO took 2319.595391511917s
Completeness | Calculation of interlinking completeness for HITO took 1.5579774379730225s
Reputation | Calculation of the PageRank for HITO took 0.020174026489257812s
Interlinking | Calculation of Degree of Connection for HITO took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for HITO took 7.82012939453125e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.1920928955078125e-06s
Believability | Calculation of trust value for HITO took 6.67572021484375e-06s
INFO | --- Analysis for hito took 2376.827527999878s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 5.859314918518066s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.2746155261993408s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 2.8133392333984375e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 7.62939453125e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 18.661216974258423s
Availability | SPARQL endpoint availability check for Homologene took 7.295608520507812e-05s
Availability | VoID file availability check for Homologene took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for Homologene took 0.7023987770080566s
Reputation | Calculation of the PageRank for Homologene took 0.020303726196289062s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Homologene took 2.7418136596679688e-05s
Believability | Calculation of trust value for Homologene took 8.106231689453125e-06s
INFO | --- Analysis for homologene took 3.311290979385376s
Availability | SPARQL endpoint availability check for gseg took 4.410743713378906e-05s
Availability | VoID file availability check for gseg took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for gseg took 0.26305675506591797s
Reputation | Calculation of the PageRank for gseg took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for gseg took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for gseg took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for gseg took 2.86102294921875e-05s
Believability | Calculation of trust value for gseg took 6.9141387939453125e-06s
INFO | --- Analysis for hongse took 3.6374127864837646s
Availability | SPARQL endpoint availability check for Noticias Universia took 4.1484832763671875e-05s
Availability | VoID file availability check for Noticias Universia took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.2812623977661133s
Reputation | Calculation of the PageRank for Noticias Universia took 0.027187347412109375s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.002025604248046875s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 5.555152893066406e-05s
Believability | Calculation of trust value for Noticias Universia took 8.344650268554688e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 3.4223921298980713s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.076957702636719e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.26707983016967773s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0008616447448730469s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.337860107421875e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 8.344650268554688e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.8960044384002686s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.4572374820709229s
Availability | VoID file availability check for COURAGE Dataset took 0.0003714561462402344s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.2592313289642334s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.0040740966796875e-05s
Believability | Calculation of trust value for COURAGE Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.591705560684204s
Availability | SPARQL endpoint availability check for RoadTrb took 4.363059997558594e-05s
Availability | VoID file availability check for RoadTrb took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2559812068939209s
Reputation | Calculation of the PageRank for RoadTrb took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for RoadTrb took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.8848648071289062e-05s
Believability | Calculation of trust value for RoadTrb took 1.0728836059570312e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.445157289505005s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.25263285636901855s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.152557373046875e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 24.402546882629395s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 5.221366882324219e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2681906223297119s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.7894973754882812e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.1682510375976562e-05s
INFO | --- Analysis for http:pakistan.com took 2.348346471786499s
Availability | SPARQL endpoint availability check for CEDICT took 4.2438507080078125e-05s
Availability | VoID file availability check for CEDICT took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for CEDICT took 0.2535831928253174s
Reputation | Calculation of the PageRank for CEDICT took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for CEDICT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CEDICT took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for CEDICT took 2.8133392333984375e-05s
Believability | Calculation of trust value for CEDICT took 7.867813110351562e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.149595499038696s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.6017625331878662s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.25547313690185547s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.723403930664062e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.3909759521484375e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.72641396522522s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.100799560546875e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.27102160453796387s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020984172821044922s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 7.62939453125e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.9075710773468018s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.38690185546875e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.24846792221069336s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.075599670410156e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.3501946926116943s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0003867149353027344s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.26465916633605957s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.8371810913085938e-05s
Believability | Calculation of trust value for Soccer Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.msm.com took 2.370363473892212s
Availability | SPARQL endpoint availability check for Game Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Game Ontology took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.251971960067749s
Reputation | Calculation of the PageRank for Game Ontology took 0.020261287689208984s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 2.7418136596679688e-05s
Believability | Calculation of trust value for Game Ontology took 7.152557373046875e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.7945261001586914s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.363059997558594e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.26787853240966797s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0236203670501709s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0012936592102050781s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.6253204345703125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.867813110351562e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.184652805328369s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.2438507080078125e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.25620293617248535s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.3676373958587646s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.315376281738281e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2812073230743408s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8848648071289062e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.3789191246032715s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 6.747245788574219e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.25952744483947754s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.956390380859375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.9141387939453125e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.3524465560913086s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 6.985664367675781e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26593923568725586s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020811080932617188s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.765655517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.9141387939453125e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.357903003692627s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.363059997558594e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2719149589538574s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.361701965332031e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.816617965698242s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 6.556510925292969e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.28449201583862305s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7894973754882812e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.9141387939453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.4488673210144043s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.410743713378906e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.2444901466369629s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 2.86102294921875e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.6689300537109375e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 3.995617628097534s
Availability | SPARQL endpoint availability check for Bookkeeping took 0.9993114471435547s
Availability | VoID file availability check for Bookkeeping took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.27623939514160156s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.147125244140625e-05s
Believability | Calculation of trust value for Bookkeeping took 1.2636184692382812e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 3.82039475440979s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Legal Ontology took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.27639102935791016s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for Legal Ontology took 7.62939453125e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.8789029121398926s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.5299530029296875e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2747507095336914s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.03169751167297363s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0012590885162353516s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 0.00010085105895996094s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 9.5367431640625e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.6883838176727295s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.506111145019531e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.26254916191101074s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 2.7894973754882812e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 7.3909759521484375e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.6714205741882324s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.172325134277344e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.2653534412384033s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.075599670410156e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 7.3909759521484375e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.9498796463012695s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.076957702636719e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2759256362915039s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 7.867813110351562e-06s
INFO | --- Analysis for hud-library-usagedata took 2.9481637477874756s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.3559165000915527s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.2726774215698242s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020394563674926758s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00011563301086425781s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 7.867813110351562e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 3.9814980030059814s
Availability | SPARQL endpoint availability check for IATE RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for IATE RDF took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2535417079925537s
Reputation | Calculation of the PageRank for IATE RDF took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.337860107421875e-05s
Believability | Calculation of trust value for IATE RDF took 7.152557373046875e-06s
INFO | --- Analysis for iate-rdf took 2.745025157928467s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.11373496055603s
Availability | VoID file availability check for IATI as Linked Data took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.24012112617492676s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.0207974910736084s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.96453857421875e-05s
Believability | Calculation of trust value for IATI as Linked Data took 7.62939453125e-06s
INFO | --- Analysis for iati-as-linked-data took 13.363832235336304s
Availability | SPARQL endpoint availability check for ICANE took 0.4383087158203125s
Availability | VoID file availability check for ICANE took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for ICANE took 0.2624516487121582s
Reputation | Calculation of the PageRank for ICANE took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for ICANE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.487701416015625e-05s
Believability | Calculation of trust value for ICANE took 5.0067901611328125e-06s
INFO | --- Analysis for icane took 3.764188766479492s
Availability | SPARQL endpoint availability check for ichoose took 0.16659259796142578s
Availability | VoID file availability check for ichoose took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for ichoose took 0.2475581169128418s
Reputation | Calculation of the PageRank for ichoose took 0.02213120460510254s
Interlinking | Calculation of Degree of Connection for ichoose took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0010662078857421875s
Interlinking | Calculation of Clustering coefficient for ichoose took 9.369850158691406e-05s
Believability | Calculation of trust value for ichoose took 7.3909759521484375e-06s
INFO | --- Analysis for ichoose took 71.4370002746582s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 1.2163310050964355s
Availability | VoID file availability check for The Iconology Dataset took 0.0003845691680908203s
Extra | Recovery of all triples for The Iconology Dataset took 5.812052488327026s
Performance | Total latancy measurement for The Iconology Dataset took 0.7439455986022949s
Amount of data | Number of triples check for The Iconology Dataset took 0.24109244346618652s
Interoperability | New terms check for The Iconology Dataset took 1.4112944602966309s
Versatility | Languages check for The Iconology Dataset took 0.6124382019042969s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.23523664474487305s
Interpretability | RDF structures check for The Iconology Dataset took 0.15335702896118164s
Versatility | Serialization formats check for The Iconology Dataset took 0.1215357780456543s
Availability | RDF dump link check for The Iconology Dataset took 0.09466314315795898s
License | MR license check for The Iconology Dataset took 0.12722992897033691s
License | HR license check for The Iconology Dataset took 0.26943397521972656s
Amount of data | Number of property check for The Iconology Dataset took 0.10663795471191406s
Understandability | Number of label check for The Iconology Dataset took 0.1622300148010254s
Understandability | URI regex check for The Iconology Dataset took 0.1725482940673828s
Understandability | Vocabs check for The Iconology Dataset took 0.0943613052368164s
Verifiability | Authors check for The Iconology Dataset took 0.10698080062866211s
Verifiability | Publishers check for The Iconology Dataset took 0.09425663948059082s
Performance | Throughput check for The Iconology Dataset took 10.29425311088562s
Amount of data | Check the number of entities for The Iconology Dataset took 8.988380432128906e-05s
Verifiability | Contribs. check for The Iconology Dataset took 0.1025850772857666s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09672951698303223s
Interlinking | skos check for The Iconology Dataset took 0.09267878532409668s
Interlinking | skos check for The Iconology Dataset took 0.09440755844116211s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09585380554199219s
Currency | Creation date check for The Iconology Dataset took 0.196913480758667s
Currency | Modification date check for The Iconology Dataset took 0.20766806602478027s
Rep.Conc. | URIs length for The Iconology Dataset took 1.2859790325164795s
Interoperability | New vocabularies check for The Iconology Dataset took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08333253860473633s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.30413341522216797s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016520261764526367s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.42841482162475586s
Consistency | Disjoint class check for The Iconology Dataset took 0.08372807502746582s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.15487074851989746s
Consistency | Misplaced classes for The Iconology Dataset took 0.854541540145874s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.6274902820587158s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.2693169116973877s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.3470001220703125s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.2922348976135254s
Security | Sign check for The Iconology Dataset took 0.08712410926818848s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2534.137776374817s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.9635152816772461s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.4543533325195312e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for The Iconology Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for iconology-dataset took 2594.0519585609436s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.363059997558594e-05s
Availability | VoID file availability check for Identifiers.org took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.2740821838378906s
Reputation | Calculation of the PageRank for Identifiers.org took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.552436828613281e-05s
Believability | Calculation of trust value for Identifiers.org took 7.3909759521484375e-06s
INFO | --- Analysis for identifiers-org took 4.336120843887329s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.2438507080078125e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2675209045410156s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.915496826171875e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 7.152557373046875e-06s
INFO | --- Analysis for idreffr took 4.408992052078247s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.9932630062103271s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.2587416172027588s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.553794860839844e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 6.9141387939453125e-06s
INFO | --- Analysis for ids took 4.892381906509399s
Availability | SPARQL endpoint availability check for ietflang took 4.3392181396484375e-05s
Availability | VoID file availability check for ietflang took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for ietflang took 0.28931307792663574s
Reputation | Calculation of the PageRank for ietflang took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for ietflang took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.410743713378906e-05s
Believability | Calculation of trust value for ietflang took 6.9141387939453125e-06s
INFO | --- Analysis for ietflang took 12.758824825286865s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.5745196342468262s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.2557651996612549s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02285909652709961s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0008265972137451172s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for IGVLL took 4.003821134567261s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.4760591983795166s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.00032138824462890625s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.9404888153076172s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9995682239532471s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.1838526725769043s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.4380507469177246s
Versatility | Languages check for 3LGM² IHE Ontology took 0.21121644973754883s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.18188047409057617s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.19454717636108398s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.20589613914489746s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.20391106605529785s
License | MR license check for 3LGM² IHE Ontology took 0.19404935836791992s
License | HR license check for 3LGM² IHE Ontology took 0.187361478805542s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.18310070037841797s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.2066037654876709s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.3752601146697998s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.18880462646484375s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.19466733932495117s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.19321417808532715s
Performance | Throughput check for 3LGM² IHE Ontology took 11.345566034317017s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.748603820800781e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.20691204071044922s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.1961359977722168s
Interlinking | skos check for 3LGM² IHE Ontology took 0.18509554862976074s
Interlinking | skos check for 3LGM² IHE Ontology took 0.19578790664672852s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.20726442337036133s
Currency | Creation date check for 3LGM² IHE Ontology took 0.3799934387207031s
Currency | Modification date check for 3LGM² IHE Ontology took 0.4031789302825928s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8363590240478516s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.19517827033996582s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.20650863647460938s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.18500161170959473s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3145174980163574s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0016009807586669922s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05019092559814453s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.19522929191589355s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4676218032836914s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.27910780906677246s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.560309648513794s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.2542355060577393s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.509805679321289s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.03072381019592285s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.19692373275756836s
Security | Sign check for 3LGM² IHE Ontology took 0.19568276405334473s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 398.4769723415375s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.32704615592956543s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 5.435943603515625e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.218650817871094e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.430511474609375e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 7.152557373046875e-06s
INFO | --- Analysis for IHE took 443.59464859962463s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.10317778587341309s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.2811751365661621s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.075599670410156e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 7.3909759521484375e-06s
INFO | --- Analysis for iislod-test took 3.7688894271850586s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.267692565917969e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.2496340274810791s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.170967102050781e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 7.867813110351562e-06s
INFO | --- Analysis for ILUSOC took 14.689483880996704s
Availability | SPARQL endpoint availability check for im@sparql took 6.876682996749878s
Availability | VoID file availability check for im@sparql took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for im@sparql took 0.7040472030639648s
Reputation | Calculation of the PageRank for im@sparql took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.123283386230469e-05s
Believability | Calculation of trust value for im@sparql took 7.3909759521484375e-06s
INFO | --- Analysis for im@sparql took 13.926329135894775s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.363059997558594e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2717413902282715s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.0517578125e-05s
Believability | Calculation of trust value for imagery bailingniao took 7.867813110351562e-06s
INFO | --- Analysis for imagery_bailingniao took 3.8127176761627197s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.167895793914795s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0003235340118408203s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 24.95612144470215s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.489694833755493s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.335384607315063s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.51282000541687s
Versatility | Languages check for Imagesnippets Image Descriptions took 10.66562294960022s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 7.29443883895874s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6665253639221191s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7174587249755859s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7031564712524414s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.6949949264526367s
License | MR license check for Imagesnippets Image Descriptions took 0.6820151805877686s
License | HR license check for Imagesnippets Image Descriptions took 10.667989015579224s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.6893701553344727s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.6554038524627686s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.3745806217193604s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.6979107856750488s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.691483736038208s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6904022693634033s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.51057744026184s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.009506225585938e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7190868854522705s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7296614646911621s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.673250675201416s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6910154819488525s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7018442153930664s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.3869457244873047s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.3813707828521729s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 31.74230933189392s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7135195732116699s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6583900451660156s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.6992185115814209s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7250802516937256s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 8.414645195007324s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 15.785884141921997s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.060600996017456s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00015544891357421875s
Security | Sign check for Imagesnippets Image Descriptions took 0.6978766918182373s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.2720985412597656s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.870529174804688e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.430511474609375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 7.62939453125e-06s
INFO | --- Analysis for imagesnippets took 256.35990142822266s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.6890459060668945s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.26106786727905273s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.0206606388092041s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 9.298324584960938e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 7.62939453125e-06s
INFO | --- Analysis for imf-linked-data took 3.6220290660858154s
Availability | SPARQL endpoint availability check for IMGpedia took 4.1484832763671875e-05s
Availability | VoID file availability check for IMGpedia took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.24251914024353027s
Reputation | Calculation of the PageRank for IMGpedia took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for IMGpedia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 2.956390380859375e-05s
Believability | Calculation of trust value for IMGpedia took 8.344650268554688e-06s
INFO | --- Analysis for imgpedia took 3.4077606201171875s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.2438507080078125e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.27808165550231934s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020252466201782227s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.9802322387695312e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 7.3909759521484375e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 3.726317882537842s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.267692565917969e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.28194761276245117s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.239776611328125e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 6.9141387939453125e-06s
INFO | --- Analysis for Imtiaz took 2.791192054748535s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.363059997558594e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.25716423988342285s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 4.220008850097656e-05s
Believability | Calculation of trust value for Royalty Free Music took 6.4373016357421875e-06s
INFO | --- Analysis for inaudio.org took 3.835258960723877s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.1961669921875e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2766549587249756s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 2.8848648071289062e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 7.62939453125e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.933061361312866s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.1961669921875e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.26603198051452637s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 2.956390380859375e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 7.3909759521484375e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.9103918075561523s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.39156341552734375s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.2550480365753174s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 3.620314836502075s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.1484832763671875e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0003058910369873047s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2706010341644287s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 5.245208740234375e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 7.867813110351562e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.8588883876800537s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 6.175041198730469e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.26632213592529297s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.02062368392944336s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00012922286987304688s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 6.9141387939453125e-06s
INFO | --- Analysis for ineverycrea took 12.662004709243774s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.5299530029296875e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2761414051055908s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.441375732421875e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 6.67572021484375e-06s
INFO | --- Analysis for ineverycrea-argentina took 7.411359548568726s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 0.049950361251831055s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007557868957519531s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.27510499954223633s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 6.794929504394531e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.152557373046875e-06s
INFO | --- Analysis for influence-tracker-dataset took 13.032225608825684s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.0531158447265625e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.26340484619140625s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 2.956390380859375e-05s
Believability | Calculation of trust value for INSEMTIVES took 1.3589859008789062e-05s
INFO | --- Analysis for insemtives took 2.9486703872680664s
Availability | SPARQL endpoint availability check for instagram.person took 4.1484832763671875e-05s
Availability | VoID file availability check for instagram.person took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for instagram.person took 0.2814493179321289s
Reputation | Calculation of the PageRank for instagram.person took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for instagram.person took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for instagram.person took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.0279159545898438e-05s
Believability | Calculation of trust value for instagram.person took 7.3909759521484375e-06s
INFO | --- Analysis for instagram_person took 2.916210651397705s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.172325134277344e-05s
Availability | VoID file availability check for instagram.videoobject took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.23814177513122559s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 2.9087066650390625e-05s
Believability | Calculation of trust value for instagram.videoobject took 6.9141387939453125e-06s
INFO | --- Analysis for instagram_videoobject took 2.8775157928466797s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2472395896911621s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 2.9802322387695312e-05s
Believability | Calculation of trust value for Instance Hub Countries took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-countries took 2.8777811527252197s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.220008850097656e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0004107952117919922s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.28192877769470215s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.0967254638671875e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 2.31550931930542s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.261430025100708s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020323514938354492s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 1.2636184692382812e-05s
INFO | --- Analysis for instance-hub-organizations took 2.9278976917266846s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub People took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.2819406986236572s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub People took 6.4373016357421875e-06s
INFO | --- Analysis for instance-hub-people took 2.952164888381958s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.38690185546875e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.27493810653686523s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.457069396972656e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 6.198883056640625e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.88860821723938s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 3.933906555175781e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.2549409866333008s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.8690507411956787s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.25501513481140137s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 1.0728836059570312e-05s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.8854751586914062s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 5.340576171875e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.27518534660339355s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 5.7220458984375e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.953479766845703s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.00021767616271972656s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2835507392883301s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 2.86102294921875e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 6.4373016357421875e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.8189594745635986s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 3.981590270996094e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0002143383026123047s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.25877928733825684s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 2.86102294921875e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 6.198883056640625e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.8092358112335205s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.2655494213104248s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 2.956390380859375e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 6.198883056640625e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.905991315841675s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.0531158447265625e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.00021505355834960938s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.25048112869262695s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.123283386230469e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 6.4373016357421875e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.8488683700561523s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.076957702636719e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.2496013641357422s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.822845458984375e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 6.198883056640625e-06s
INFO | --- Analysis for interactivemaps-gnoss took 9.38306975364685s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.5299530029296875e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2733945846557617s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 2.956390380859375e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 6.198883056640625e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.8976056575775146s
Availability | SPARQL endpoint availability check for intervalue took 0.13166356086730957s
Availability | VoID file availability check for intervalue took 0.0003230571746826172s
Completeness | Calculation of interlinking completeness for intervalue took 0.2540738582611084s
Reputation | Calculation of the PageRank for intervalue took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.866455078125e-05s
Believability | Calculation of trust value for intervalue took 6.67572021484375e-06s
INFO | --- Analysis for intervalue took 2.504199743270874s
Availability | SPARQL endpoint availability check for Inztrow took 4.100799560546875e-05s
Availability | VoID file availability check for Inztrow took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2978806495666504s
Reputation | Calculation of the PageRank for Inztrow took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.361701965332031e-05s
Believability | Calculation of trust value for Inztrow took 9.059906005859375e-06s
INFO | --- Analysis for Inztrow took 3.618178367614746s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2642979621887207s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 8.106231689453125e-06s
INFO | --- Analysis for ipbes took 3.77665638923645s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.553794860839844e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.28733348846435547s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.3392181396484375e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 6.9141387939453125e-06s
INFO | --- Analysis for iptc-newscodes took 3.30782151222229s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.981590270996094e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.28527164459228516s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.147125244140625e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 6.4373016357421875e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.927658796310425s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.2811741828918457s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.001316070556640625s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.2626063823699951s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.965896606445312e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.2159347534179688e-05s
INFO | --- Analysis for iserve took 8.92273211479187s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.983783721923828s
Availability | VoID file availability check for ISIC V4 took 0.0010123252868652344s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.28064942359924316s
Reputation | Calculation of the PageRank for ISIC V4 took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.600120544433594e-05s
Believability | Calculation of trust value for ISIC V4 took 5.245208740234375e-06s
INFO | --- Analysis for isic-v4 took 115.47549033164978s
Availability | SPARQL endpoint availability check for Isidore took 5.030632019042969e-05s
Availability | VoID file availability check for Isidore took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Isidore took 0.271695613861084s
Reputation | Calculation of the PageRank for Isidore took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for Isidore took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Isidore took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Isidore took 2.9802322387695312e-05s
Believability | Calculation of trust value for Isidore took 8.106231689453125e-06s
INFO | --- Analysis for isidore took 2.902301549911499s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.267692565917969e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2834126949310303s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.605552673339844e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 5.7220458984375e-06s
INFO | --- Analysis for isil-dbpedia took 4.585521936416626s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 5.8650970458984375e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.26710009574890137s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.981590270996094e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 7.867813110351562e-06s
INFO | --- Analysis for iso-3166-2-data took 2.8614487648010254s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.458427429199219e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.27109742164611816s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.647804260253906e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 6.9141387939453125e-06s
INFO | --- Analysis for iso-639-oasis took 2.911874532699585s
Availability | SPARQL endpoint availability check for ISOcat took 4.2438507080078125e-05s
Availability | VoID file availability check for ISOcat took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for ISOcat took 0.38966965675354004s
Reputation | Calculation of the PageRank for ISOcat took 0.02281808853149414s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.604194641113281e-05s
Believability | Calculation of trust value for ISOcat took 1.3113021850585938e-05s
INFO | --- Analysis for isocat took 33.24063539505005s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.553794860839844e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.00035071372985839844s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.2448289394378662s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.000980377197265625s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 4.1961669921875e-05s
Believability | Calculation of trust value for ISOcat-metadata took 7.867813110351562e-06s
INFO | --- Analysis for isocat-metadata took 4.78029990196228s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.2438507080078125e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.25903820991516113s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.021100521087646484s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.314018249511719e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.882673501968384s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3069937229156494s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00043010711669921875s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.228866338729858s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7720987796783447s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20636200904846191s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.041619300842285s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.3583734035492s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24486231803894043s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09677886962890625s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1891474723815918s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1759204864501953s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14970088005065918s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2394392490386963s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.7230794429779s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19480490684509277s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.094484806060791s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4360532760620117s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19569969177246094s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20239019393920898s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1438438892364502s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.744796514511108s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.271766662597656e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19295167922973633s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2736244201660156s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.46167922019958496s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4673588275909424s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20069456100463867s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31619954109191895s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15197396278381348s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 14.876848220825195s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14359807968139648s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15710186958312988s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15424370765686035s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.364482641220093s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3121516704559326s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.26582837104797363s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16606616973876953s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.71204686164856s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9997563362121582s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.945734262466431s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3174424171447754s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 11.002348899841309s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2906363010406494s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17248773574829102s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18536996841430664s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.65343189239502s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3921058177947998s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.942054748535156e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-place took 466.187885761261s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.696846008300781e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2507646083831787s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.123283386230469e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-rmn took 3.7787582874298096s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.13484430313110352s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0006101131439208984s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 9.144438743591309s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.8056097030639648s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.21376252174377441s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 3.049373149871826s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 91.05895256996155s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.20235371589660645s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.10758209228515625s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.19770431518554688s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.16283011436462402s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.15029644966125488s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.22013568878173828s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 92.23734259605408s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.2061748504638672s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.1610431671142578s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.40607118606567383s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.19870400428771973s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.18320751190185547s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.16263413429260254s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.622896432876587s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 8.296966552734375e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.19890189170837402s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.27770543098449707s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.45188093185424805s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.461076021194458s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.17031145095825195s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.30991411209106445s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.1350700855255127s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 15.433054208755493s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.1419081687927246s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.14437389373779297s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.15771937370300293s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 4.821326017379761s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.306732177734375s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.27982163429260254s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.12787461280822754s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.72726845741272s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9520764350891113s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 4.804029941558838s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.314443588256836s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.98458480834961s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2861487865447998s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.1577436923980713s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.18155503273010254s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.533433675765991s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.44037723541259766s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-ron took 462.48482513427734s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 7.033348083496094e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.2747519016265869s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.1948089599609375e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-sc took 3.7625436782836914s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6863305568695068s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2598850727081299s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.489059448242188e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for issa-agritrop took 5.678175687789917s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.3392181396484375e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.23709392547607422s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.0517578125e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.3909759521484375e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.827308177947998s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.315376281738281e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2715940475463867s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.0040740966796875e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.1920928955078125e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 2.9686787128448486s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.410743713378906e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.25609827041625977s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020394086837768555s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 2.9802322387695312e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 6.4373016357421875e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 2.54986572265625s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.9691295623779297s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0011150836944580078s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.6911015510559082s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020263195037841797s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 9.059906005859375e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.0067901611328125e-06s
INFO | --- Analysis for istat-immigration took 4.763093948364258s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 5.1975250244140625e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.26641416549682617s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020815372467041016s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 4.1484832763671875e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 7.62939453125e-06s
INFO | --- Analysis for istat-immigrazione took 2.938476324081421s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.4486427307128906s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2687838077545166s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.1948089599609375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 4.5299530029296875e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.0725693702697754s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.0604925155639648s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0012013912200927734s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2604084014892578s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.724761962890625e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 7.152557373046875e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 3.5021145343780518s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.172325134277344e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.24370384216308594s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.123283386230469e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 8.106231689453125e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.8522307872772217s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.696846008300781e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.27517175674438477s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.409385681152344e-05s
Believability | Calculation of trust value for IWMI Research Reports took 7.3909759521484375e-06s
INFO | --- Analysis for iwmi-research-reports took 2.911487340927124s
Availability | SPARQL endpoint availability check for IWN took 4.291534423828125e-05s
Availability | VoID file availability check for IWN took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for IWN took 0.2582995891571045s
Reputation | Calculation of the PageRank for IWN took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for IWN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IWN took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for IWN took 3.790855407714844e-05s
Believability | Calculation of trust value for IWN took 5.9604644775390625e-06s
INFO | --- Analysis for iwn took 5.875881671905518s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.220008850097656e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.2627229690551758s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.170967102050781e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 7.62939453125e-06s
INFO | --- Analysis for j-global-knowledge took 2.9640119075775146s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 8.082389831542969e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.26194238662719727s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 3.0994415283203125e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 7.3909759521484375e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.969491720199585s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.265521049499512s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0009005069732666016s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2633383274078369s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.651878356933594e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 7.62939453125e-06s
INFO | --- Analysis for jamendo-dbtune took 25.37934160232544s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.291534423828125e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0013031959533691406s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2682523727416992s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020179033279418945s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.673004150390625e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.290584325790405s
Availability | SPARQL endpoint availability check for JEL Classification took 4.38690185546875e-05s
Availability | VoID file availability check for JEL Classification took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2768855094909668s
Reputation | Calculation of the PageRank for JEL Classification took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.886222839355469e-05s
Believability | Calculation of trust value for JEL Classification took 7.867813110351562e-06s
INFO | --- Analysis for jel-classification took 4.705343723297119s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.2360053062438965s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.30191493034362793s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.0517578125e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 7.867813110351562e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.016956567764282s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 260.79298424720764s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.2788057327270508s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.581710815429688e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 6.9141387939453125e-06s
INFO | --- Analysis for jita took 541.6781942844391s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.124641418457031e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.7644007205963135s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 2.9087066650390625e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.867813110351562e-06s
INFO | --- Analysis for jmdict took 5.090775489807129s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.071125268936157s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.2939491271972656s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.441375732421875e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.152557373046875e-06s
INFO | --- Analysis for john-goodwins-family-tree took 63.96295642852783s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.267692565917969e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.25822997093200684s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.4332275390625e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 8.58306884765625e-06s
INFO | --- Analysis for jp-cos took 4.734492301940918s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.267692565917969e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.26083898544311523s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020605087280273438s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.482269287109375e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 7.62939453125e-06s
INFO | --- Analysis for jp-textbook took 4.367971181869507s
Availability | SPARQL endpoint availability check for JRC-Names took 4.458427429199219e-05s
Availability | VoID file availability check for JRC-Names took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.3011472225189209s
Reputation | Calculation of the PageRank for JRC-Names took 0.020948410034179688s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0010313987731933594s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 4.363059997558594e-05s
Believability | Calculation of trust value for JRC-Names took 7.3909759521484375e-06s
INFO | --- Analysis for jrc-names-ec took 5.202074766159058s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.4234645366668701s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.2671535015106201s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.937980651855469e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 8.58306884765625e-06s
INFO | --- Analysis for jrc-names-mlode took 4.388216733932495s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.3392181396484375e-05s
Availability | VoID file availability check for JudaicaLink took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.25375795364379883s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for JudaicaLink took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00011420249938964844s
Believability | Calculation of trust value for JudaicaLink took 6.9141387939453125e-06s
INFO | --- Analysis for judaicalink took 22.531694173812866s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.124641418457031e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.2582817077636719s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.02089691162109375s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0009686946868896484s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.218650817871094e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 7.867813110351562e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.9179303646087646s
Availability | SPARQL endpoint availability check for KAKEN took 4.1961669921875e-05s
Availability | VoID file availability check for KAKEN took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for KAKEN took 0.27994799613952637s
Reputation | Calculation of the PageRank for KAKEN took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for KAKEN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for KAKEN took 0.0008542537689208984s
Interlinking | Calculation of Clustering coefficient for KAKEN took 2.9802322387695312e-05s
Believability | Calculation of trust value for KAKEN took 8.106231689453125e-06s
INFO | --- Analysis for kaken took 2.966240882873535s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06726956367492676s
Availability | VoID file availability check for Kallikratis municipalities took 0.00037741661071777344s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.26111936569213867s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020259380340576172s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.179115295410156e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 4.76837158203125e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.4479007720947266s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.172325134277344e-05s
Availability | VoID file availability check for Openflights Routes took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.2751908302307129s
Reputation | Calculation of the PageRank for Openflights Routes took 0.020270347595214844s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 2.9325485229492188e-05s
Believability | Calculation of trust value for Openflights Routes took 7.62939453125e-06s
INFO | --- Analysis for kasabi-openflights-routes took 3.3781988620758057s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.267692565917969e-05s
Availability | VoID file availability check for EU Soccer League took 0.001424551010131836s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.28108644485473633s
Reputation | Calculation of the PageRank for EU Soccer League took 0.02019500732421875s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 2.956390380859375e-05s
Believability | Calculation of trust value for EU Soccer League took 7.3909759521484375e-06s
INFO | --- Analysis for KG:Course_Submission took 3.489777088165283s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.291534423828125e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.25295209884643555s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.2159347534179688e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.1205673217773438e-05s
INFO | --- Analysis for KING took 2.5819826126098633s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.2438507080078125e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2793598175048828s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 7.343292236328125e-05s
Believability | Calculation of trust value for Klappstuhlclub took 4.291534423828125e-06s
INFO | --- Analysis for klappstuhlclub took 12.518632173538208s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.838298082351685s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2892460823059082s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020994186401367188s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.556510925292969e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 7.62939453125e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.298017501831055s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.076957702636719e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2610654830932617s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020434141159057617s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.0517578125e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.71661376953125e-05s
INFO | --- Analysis for knowledge-map took 2.8495800495147705s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.3392181396484375e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2595193386077881s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02070307731628418s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.695487976074219e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.1444091796875e-05s
INFO | --- Analysis for KnowledgeFusion took 2.4201459884643555s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.38690185546875e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.27840590476989746s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.794929504394531e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 6.67572021484375e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.28219985961914s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.124641418457031e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.27501440048217773s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.021114349365234375s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0008642673492431641s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.361701965332031e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 7.3909759521484375e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.978588104248047s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 5.14984130859375e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.26282262802124023s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.0040740966796875e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 6.9141387939453125e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.3545005321502686s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.1484832763671875e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.27609992027282715s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 2.9325485229492188e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 7.62939453125e-06s
INFO | --- Analysis for ktr took 2.9324018955230713s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.3392181396484375e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.25917553901672363s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.9087066650390625e-05s
Believability | Calculation of trust value for Informatics Studies took 6.9141387939453125e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.9975223541259766s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.057498931884765625s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.25737500190734863s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.62396240234375e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for kupkb took 9.666188716888428s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.220008850097656e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.244492769241333s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 2.8371810913085938e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 7.152557373046875e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.8850150108337402s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.251746654510498s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2720491886138916s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.224082946777344e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 7.3909759521484375e-06s
INFO | --- Analysis for l3s-dblp took 49.01572823524475s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.52122211456299s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.27031373977661133s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020865201950073242s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 7.557868957519531e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.239776611328125e-05s
INFO | --- Analysis for lak-dataset took 67.47056865692139s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.2995944023132324s
Availability | VoID file availability check for  Language Name Authority List  took 0.0006127357482910156s
Extra | Recovery of all triples for  Language Name Authority List  took 128.60315465927124s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6272804737091064s
Amount of data | Number of triples check for  Language Name Authority List  took 0.5262515544891357s
Interoperability | New terms check for  Language Name Authority List  took 12.04691767692566s
Versatility | Languages check for  Language Name Authority List  took 300.00674843788147s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 2.7426869869232178s
Security | Check HTTPS for  Language Name Authority List  took 0.32625365257263184s
Interpretability | RDF structures check for  Language Name Authority List  took 0.40767383575439453s
Versatility | Serialization formats check for  Language Name Authority List  took 3.8982255458831787s
Availability | RDF dump link check for  Language Name Authority List  took 0.23616361618041992s
License | MR license check for  Language Name Authority List  took 0.16361689567565918s
License | HR license check for  Language Name Authority List  took 300.104465007782s
Amount of data | Number of property check for  Language Name Authority List  took 0.18545150756835938s
Understandability | Number of label check for  Language Name Authority List  took 0.8037018775939941s
Understandability | URI regex check for  Language Name Authority List  took 0.2300107479095459s
Understandability | Vocabs check for  Language Name Authority List  took 0.1255049705505371s
Verifiability | Authors check for  Language Name Authority List  took 0.2027149200439453s
Verifiability | Publishers check for  Language Name Authority List  took 0.1724686622619629s
Performance | Throughput check for  Language Name Authority List  took 10.691851615905762s
Amount of data | Check the number of entities for  Language Name Authority List  took 7.82012939453125e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.17614245414733887s
Interlinking | sameAs chians check for  Language Name Authority List  took 0.9993500709533691s
Interlinking | skos check for  Language Name Authority List  took 0.14856934547424316s
Interlinking | skos check for  Language Name Authority List  took 0.11363649368286133s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.20587778091430664s
Currency | Creation date check for  Language Name Authority List  took 0.2829277515411377s
Currency | Modification date check for  Language Name Authority List  took 0.15678191184997559s
Rep.Conc. | URIs length for  Language Name Authority List  took 198.15316772460938s
Interoperability | New vocabularies check for  Language Name Authority List  took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.16204285621643066s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.2668123245239258s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.1571791172027588s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 34.03486156463623s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.2415010929107666s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.7040750980377197s
Consistency | Disjoint class check for  Language Name Authority List  took 0.17769908905029297s
Consistency | Check Misplaced properties for  Language Name Authority List  took 55.593909740448s
Consistency | Misplaced classes for  Language Name Authority List  took 8.369724035263062s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 32.83996510505676s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.4389581680297852s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 56.90253400802612s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 2.9970016479492188s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.43152284622192383s
Security | Sign check for  Language Name Authority List  took 0.12250518798828125s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 9.461649417877197s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.7050871849060059s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021039247512817383s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.179115295410156e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 2.6226043701171875e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 7.867813110351562e-06s
INFO | --- Analysis for language-authority-list took 15949.093902349472s
Availability | SPARQL endpoint availability check for Lark took 385.01993107795715s
Availability | VoID file availability check for Lark took 0.0008141994476318359s
Completeness | Calculation of interlinking completeness for Lark took 0.8570082187652588s
Reputation | Calculation of the PageRank for Lark took 0.02064204216003418s
Interlinking | Calculation of Degree of Connection for Lark took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Lark took 8.296966552734375e-05s
Believability | Calculation of trust value for Lark took 7.3909759521484375e-06s
INFO | --- Analysis for LARK took 1679.5521717071533s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 60.40320301055908s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.26372456550598145s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.172325134277344e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for LASLA took 66.53492283821106s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.172325134277344e-05s
Availability | VoID file availability check for LATC Linksets took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.2672309875488281s
Reputation | Calculation of the PageRank for LATC Linksets took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 2.8133392333984375e-05s
Believability | Calculation of trust value for LATC Linksets took 7.152557373046875e-06s
INFO | --- Analysis for latc-linksets took 3.8867647647857666s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.26325011253356934s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.2731668949127197s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 4.193828582763672s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 210.78942227363586s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.277773380279541s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 4.458427429199219e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for LatinAffectus took 345.183230638504s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 180.41235756874084s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0003859996795654297s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.3206512928009033s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 5.793571472167969e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for LatinWordnetLiLa took 375.00265645980835s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.1484832763671875e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.27503204345703125s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 7.62939453125e-06s
INFO | --- Analysis for lcc took 3.48828125s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.2438507080078125e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0007507801055908203s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2589735984802246s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02020859718322754s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011754035949707031s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.1682510375976562e-05s
INFO | --- Analysis for lcsh took 17.16701316833496s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.220008850097656e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.3038480281829834s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020472288131713867s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.7738037109375e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 8.106231689453125e-06s
INFO | --- Analysis for lcsubjects took 10.782402276992798s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.172325134277344e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.24937891960144043s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0009603500366210938s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.552436828613281e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 8.344650268554688e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 3.478543281555176s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.749377727508545s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.2586843967437744s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.1484832763671875e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.239776611328125e-05s
INFO | --- Analysis for ldt@library took 36.519999265670776s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.1961669921875e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.2643129825592041s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.02027606964111328s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 2.8133392333984375e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 8.344650268554688e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.935486316680908s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.1484832763671875e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.2727057933807373s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 3.0517578125e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 7.867813110351562e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.805962324142456s
Availability | SPARQL endpoint availability check for U ime Legije took 4.3392181396484375e-05s
Availability | VoID file availability check for U ime Legije took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.29339146614074707s
Reputation | Calculation of the PageRank for U ime Legije took 0.020364046096801758s
Interlinking | Calculation of Degree of Connection for U ime Legije took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 2.9802322387695312e-05s
Believability | Calculation of trust value for U ime Legije took 8.106231689453125e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.4563333988189697s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.458427429199219e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0003230571746826172s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.2930750846862793s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 2.8133392333984375e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 7.867813110351562e-06s
INFO | --- Analysis for legislation-openuplabs took 2.887913465499878s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 194.82668471336365s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0008475780487060547s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.38246750831604004s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.939338684082031e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 7.3909759521484375e-06s
INFO | --- Analysis for LemmaBank took 570.5750048160553s
Availability | SPARQL endpoint availability check for lemonUby took 8.654594421386719e-05s
Availability | VoID file availability check for lemonUby took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for lemonUby took 0.28162336349487305s
Reputation | Calculation of the PageRank for lemonUby took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0009434223175048828s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.723403930664062e-05s
Believability | Calculation of trust value for lemonUby took 1.6927719116210938e-05s
INFO | --- Analysis for lemonuby took 4.12593150138855s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.291534423828125e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.29210472106933594s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.337860107421875e-05s
Believability | Calculation of trust value for LemonWiktionary took 8.344650268554688e-06s
INFO | --- Analysis for lemonwiktionary took 6.291308641433716s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 180.3759250640869s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.29320597648620605s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 5.078315734863281e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for LewisShort took 314.4630870819092s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 20.324827432632446s
Availability | VoID file availability check for LEXIN-RDF took 0.001299142837524414s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2742125988006592s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020944595336914062s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for LEXIN-RDF took 7.152557373046875e-06s
INFO | --- Analysis for lexin-rdf took 55.76843214035034s
Availability | SPARQL endpoint availability check for lexinfo took 4.4345855712890625e-05s
Availability | VoID file availability check for lexinfo took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for lexinfo took 0.24497103691101074s
Reputation | Calculation of the PageRank for lexinfo took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.000957489013671875s
Interlinking | Calculation of Clustering coefficient for lexinfo took 0.00010895729064941406s
Believability | Calculation of trust value for lexinfo took 1.621246337890625e-05s
INFO | --- Analysis for lexinfo took 2.943889856338501s
Availability | SPARQL endpoint availability check for Lexvo took 4.696846008300781e-05s
Availability | VoID file availability check for Lexvo took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2701592445373535s
Reputation | Calculation of the PageRank for Lexvo took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00018286705017089844s
Believability | Calculation of trust value for Lexvo took 9.5367431640625e-06s
INFO | --- Analysis for lexvo took 42.90545344352722s
Availability | SPARQL endpoint availability check for Lexvo.org took 5.626678466796875e-05s
Availability | VoID file availability check for Lexvo.org took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.29805493354797363s
Reputation | Calculation of the PageRank for Lexvo.org took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.343292236328125e-05s
Believability | Calculation of trust value for Lexvo.org took 6.67572021484375e-06s
INFO | --- Analysis for lexvo-org took 22.997724294662476s
Availability | SPARQL endpoint availability check for LIBRIS took 0.39682555198669434s
Availability | VoID file availability check for LIBRIS took 0.0006136894226074219s
Extra | Recovery of all triples for LIBRIS took 19.871047496795654s
Performance | Total latancy measurement for LIBRIS took 0.7558755874633789s
Amount of data | Number of triples check for LIBRIS took 22.311206579208374s
Interoperability | New terms check for LIBRIS took 15.435343742370605s
Versatility | Languages check for LIBRIS took 0.19331979751586914s
Interpretability | Number of blank nodes check for LIBRIS took 300.0927858352661s
Security | Check HTTPS for LIBRIS took 0.3394136428833008s
Interpretability | RDF structures check for LIBRIS took 0.4345433712005615s
Versatility | Serialization formats check for LIBRIS took 0.29564404487609863s
Availability | RDF dump link check for LIBRIS took 0.1692211627960205s
License | MR license check for LIBRIS took 0.38466835021972656s
License | HR license check for LIBRIS took 0.296536922454834s
Amount of data | Number of property check for LIBRIS took 0.21544647216796875s
Understandability | Number of label check for LIBRIS took 0.7682914733886719s
Understandability | URI regex check for LIBRIS took 0.4456026554107666s
Understandability | Vocabs check for LIBRIS took 0.15806150436401367s
Verifiability | Authors check for LIBRIS took 0.21602487564086914s
Verifiability | Publishers check for LIBRIS took 0.19960236549377441s
Performance | Throughput check for LIBRIS took 11.091960906982422s
Amount of data | Check the number of entities for LIBRIS took 6.937980651855469e-05s
Verifiability | Contribs. check for LIBRIS took 0.2010490894317627s
Interlinking | sameAs chians check for LIBRIS took 0.23882508277893066s
Interlinking | skos check for LIBRIS took 0.37097930908203125s
Interlinking | skos check for LIBRIS took 0.1347205638885498s
Timeliness | dataset update frequency check for LIBRIS took 0.21596217155456543s
Currency | Creation date check for LIBRIS took 0.40256357192993164s
Currency | Modification date check for LIBRIS took 0.6412808895111084s
Rep.Conc. | URIs length for LIBRIS took 88.23137378692627s
Interoperability | New vocabularies check for LIBRIS took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.1972951889038086s
Accuracy | Check Functional Property for LIBRIS took 0.21047306060791016s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.1472938060760498s
Accuracy | Check Datatype consistency for LIBRIS took 0.2846519947052002s
Consistency | Disjoint class check for LIBRIS took 0.18523693084716797s
Consistency | Check Misplaced properties for LIBRIS took 62.3091824054718s
Consistency | Misplaced classes for LIBRIS took 1.2131507396697998s
Consistency | Check Ontology hijacking for LIBRIS took 6.903261661529541s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3095958232879639s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 62.09314012527466s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2846088409423828s
Conciseness | Check Intensional conciseness for LIBRIS took 0.4444766044616699s
Security | Sign check for LIBRIS took 0.33681321144104004s
Availability | Check URIs Dereferenciability for LIBRIS took 10.491725444793701s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.9951531887054443s
Reputation | Calculation of the PageRank for LIBRIS took 0.020064115524291992s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00010132789611816406s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.1920928955078125e-06s
Believability | Calculation of trust value for LIBRIS took 7.3909759521484375e-06s
INFO | --- Analysis for libris took 1097.6146564483643s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.05917096138000488s
Availability | VoID file availability check for Public Library of Veroia took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.28880953788757324s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.915496826171875e-05s
Believability | Calculation of trust value for Public Library of Veroia took 7.62939453125e-06s
INFO | --- Analysis for libver took 4.545076608657837s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.09893202781677246s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0011568069458007812s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.264509916305542s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 0.00010251998901367188s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.245208740234375e-06s
INFO | --- Analysis for lichfield-spending took 2.9336998462677s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.553794860839844e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.2597827911376953s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0008552074432373047s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.5762786865234375e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 6.9141387939453125e-06s
INFO | --- Analysis for lime took 6.6570398807525635s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.363059997558594e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007596015930175781s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.27475452423095703s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02608346939086914s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0011773109436035156s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0001621246337890625s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 8.106231689453125e-06s
INFO | --- Analysis for lingvoj took 4.795320272445679s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.363059997558594e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.24728107452392578s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Crunchbase took 7.62939453125e-06s
INFO | --- Analysis for linked-crunchbase took 2.9164628982543945s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 9.464720249176025s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007750988006591797s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.24587249755859375s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.916854858398438e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.867813110351562e-06s
INFO | --- Analysis for linked-drugs took 22.664265155792236s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.363059997558594e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.2638404369354248s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.022355079650878906s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0008299350738525391s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.00010561943054199219s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 4.76837158203125e-06s
INFO | --- Analysis for linked-edgar took 4.022862434387207s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.601478576660156e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.2610158920288086s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020957231521606445s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.679794311523438e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-eurostat took 4.159123182296753s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.38690185546875e-05s
Availability | VoID file availability check for linked hypernyms took 0.0013289451599121094s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2765359878540039s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.534027099609375e-05s
Believability | Calculation of trust value for linked hypernyms took 7.62939453125e-06s
INFO | --- Analysis for linked-hypernyms took 3.4085354804992676s
Availability | SPARQL endpoint availability check for Linked Life Data took 209.69360637664795s
Availability | VoID file availability check for Linked Life Data took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.29913330078125s
Reputation | Calculation of the PageRank for Linked Life Data took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.435943603515625e-05s
Believability | Calculation of trust value for Linked Life Data took 7.152557373046875e-06s
INFO | --- Analysis for linked-life-data took 685.8078949451447s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.4960334300994873s
Availability | VoID file availability check for Linked Logainm took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.7170157432556152s
Reputation | Calculation of the PageRank for Linked Logainm took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.486343383789062e-05s
Believability | Calculation of trust value for Linked Logainm took 7.867813110351562e-06s
INFO | --- Analysis for linked-logainm took 4.495171546936035s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.458427429199219e-05s
Availability | VoID file availability check for Linked NUTS took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.2570474147796631s
Reputation | Calculation of the PageRank for Linked NUTS took 0.022170543670654297s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0008945465087890625s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 6.461143493652344e-05s
Believability | Calculation of trust value for Linked NUTS took 5.245208740234375e-06s
INFO | --- Analysis for linked-nuts took 3.343553066253662s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.26755738258361816s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020336151123046875s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 7.62939453125e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 3.9448227882385254s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.839615821838379s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.2738945484161377s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.504753112792969e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.4836273193359375e-06s
INFO | --- Analysis for linked-open-camera took 4.8136608600616455s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 3.504483938217163s
Availability | VoID file availability check for Linked Open Commerce took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.27436280250549316s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 2.7894973754882812e-05s
Believability | Calculation of trust value for Linked Open Commerce took 7.62939453125e-06s
INFO | --- Analysis for linked-open-commerce took 13.721807956695557s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.327146291732788s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.27044677734375s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00011205673217773438s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.7881393432617188e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 3.842214822769165s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.27016210556030273s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.845329284667969e-05s
Believability | Calculation of trust value for Linked Open Numbers took 7.867813110351562e-06s
INFO | --- Analysis for linked-open-numbers took 2.6536307334899902s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.28015828132629395s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-piracy took 7.345089912414551s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.124641418457031e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.26476097106933594s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 8.106231689453125e-06s
INFO | --- Analysis for linked-open-senate took 3.076192617416382s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 3.1713435649871826s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.278684139251709s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.792213439941406e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 7.152557373046875e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 32.717987060546875s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.24881529808044434s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.743171691894531e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.7220458984375e-06s
INFO | --- Analysis for linked-periodicals took 2.495321750640869s
Availability | SPARQL endpoint availability check for Linked Index took 4.3392181396484375e-05s
Availability | VoID file availability check for Linked Index took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Linked Index took 0.29054713249206543s
Reputation | Calculation of the PageRank for Linked Index took 0.0210111141204834s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Linked Index took 9.417533874511719e-05s
Believability | Calculation of trust value for Linked Index took 8.344650268554688e-06s
INFO | --- Analysis for linked-stockindex took 2.4417386054992676s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.082940101623535s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2546415328979492s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 4.506111145019531e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 8.58306884765625e-06s
INFO | --- Analysis for linked-structured-product-labels took 11.921069383621216s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.11635065078735352s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2458200454711914s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0010066032409667969s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 4.38690185546875e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 7.867813110351562e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 2.5387721061706543s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.169960260391235s
Availability | VoID file availability check for Linked TCGA took 0.001241445541381836s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.2734091281890869s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02080821990966797s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.368492126464844e-05s
Believability | Calculation of trust value for Linked TCGA took 7.3909759521484375e-06s
INFO | --- Analysis for linked-tcga took 62.80132341384888s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.21865630149841309s
Availability | VoID file availability check for Linked User Feedback took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.32202792167663574s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.933906555175781e-05s
Believability | Calculation of trust value for Linked User Feedback took 6.9141387939453125e-06s
INFO | --- Analysis for linked-user-feedback took 2.776230573654175s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.3392181396484375e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0011703968048095703s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2526888847351074s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.62939453125e-05s
Believability | Calculation of trust value for USPTO Patent data took 7.152557373046875e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.301780700683594s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.28323912620544434s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020418167114257812s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 7.152557373046875e-06s
INFO | --- Analysis for linked-web-apis took 3.3591272830963135s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.291534423828125e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.2651329040527344s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.457069396972656e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 7.3909759521484375e-06s
INFO | --- Analysis for linkedarc took 2.914762496948242s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.06124591827392578s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.24531078338623047s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020262718200683594s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.4066696166992188e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 2.744138717651367s
Availability | SPARQL endpoint availability check for LinkedCT took 1.6089887619018555s
Availability | VoID file availability check for LinkedCT took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.2736668586730957s
Reputation | Calculation of the PageRank for LinkedCT took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for LinkedCT took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.870529174804688e-05s
Believability | Calculation of trust value for LinkedCT took 7.152557373046875e-06s
INFO | --- Analysis for linkedct took 5.435771465301514s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.22131991386413574s
Availability | VoID file availability check for LinkedGeoData took 0.0006003379821777344s
Extra | Recovery of all triples for LinkedGeoData took 15.10954737663269s
Performance | Total latancy measurement for LinkedGeoData took 0.7048280239105225s
Amount of data | Number of triples check for LinkedGeoData took 47.4665744304657s
Interoperability | New terms check for LinkedGeoData took 91.29412198066711s
Versatility | Languages check for LinkedGeoData took 181.40592074394226s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.22007393836975098s
Security | Check HTTPS for LinkedGeoData took 0.34126758575439453s
Interpretability | RDF structures check for LinkedGeoData took 0.8182036876678467s
Versatility | Serialization formats check for LinkedGeoData took 0.32843613624572754s
Availability | RDF dump link check for LinkedGeoData took 0.16450858116149902s
License | MR license check for LinkedGeoData took 0.5869112014770508s
License | HR license check for LinkedGeoData took 88.12381744384766s
Amount of data | Number of property check for LinkedGeoData took 0.25937652587890625s
Understandability | Number of label check for LinkedGeoData took 2.087779998779297s
Understandability | URI regex check for LinkedGeoData took 0.3912997245788574s
Understandability | Vocabs check for LinkedGeoData took 0.1754436492919922s
Verifiability | Authors check for LinkedGeoData took 0.15880489349365234s
Verifiability | Publishers check for LinkedGeoData took 0.12630724906921387s
Performance | Throughput check for LinkedGeoData took 10.740412712097168s
Amount of data | Check the number of entities for LinkedGeoData took 0.06412124633789062s
Verifiability | Contribs. check for LinkedGeoData took 2.0655887126922607s
Interlinking | sameAs chians check for LinkedGeoData took 0.27974390983581543s
Interlinking | skos check for LinkedGeoData took 0.372952938079834s
Interlinking | skos check for LinkedGeoData took 0.13205742835998535s
Timeliness | dataset update frequency check for LinkedGeoData took 0.32744622230529785s
Currency | Creation date check for LinkedGeoData took 0.45751047134399414s
Currency | Modification date check for LinkedGeoData took 2.500863790512085s
Rep.Conc. | URIs length for LinkedGeoData took 271.9367866516113s
Interoperability | New vocabularies check for LinkedGeoData took 98.1008870601654s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.17734813690185547s
Accuracy | Check Functional Property for LinkedGeoData took 0.19735932350158691s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.1829056739807129s
Accuracy | Check Empty annotation labels for LinkedGeoData took 3.0446650981903076s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15402436256408691s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.1406388282775879s
Consistency | Disjoint class check for LinkedGeoData took 0.21909761428833008s
Consistency | Check Misplaced properties for LinkedGeoData took 180.60283422470093s
Consistency | Misplaced classes for LinkedGeoData took 0.6594395637512207s
Consistency | Check Ontology hijacking for LinkedGeoData took 4.951892375946045s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.3273134231567383s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.1704339981079s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.1489400863647461s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.3270998001098633s
Security | Sign check for LinkedGeoData took 0.6098785400390625s
Availability | Check URIs Dereferenciability for LinkedGeoData took 11.841703176498413s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 1.5186269283294678s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020806074142456055s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.0001342296600341797s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 89.55746936798096s
Believability | Calculation of trust value for LinkedGeoData took 7.62939453125e-06s
INFO | --- Analysis for linkedgeodata took 2331.5165996551514s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 5.698204040527344e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.27603912353515625s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 2.9802322387695312e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 7.62939453125e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 3.014594793319702s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.0880303382873535s
Availability | VoID file availability check for LinkedLCCN took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.26203107833862305s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010633468627929688s
Believability | Calculation of trust value for LinkedLCCN took 7.152557373046875e-06s
INFO | --- Analysis for linkedlccn took 12.790770530700684s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.553794860839844e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.26189708709716797s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.361701965332031e-05s
Believability | Calculation of trust value for LinkedMarkMail took 7.152557373046875e-06s
INFO | --- Analysis for linkedmarkmail took 3.0984346866607666s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.658501386642456s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.28201961517333984s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00014734268188476562s
Believability | Calculation of trust value for Linked Movie DataBase took 7.152557373046875e-06s
INFO | --- Analysis for linkedmdb took 133.82888650894165s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.4555032253265381s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.2457575798034668s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.271766662597656e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for linkedspending took 4.981235980987549s
Availability | SPARQL endpoint availability check for LinkedStats took 4.2438507080078125e-05s
Availability | VoID file availability check for LinkedStats took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.284515380859375s
Reputation | Calculation of the PageRank for LinkedStats took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 4.124641418457031e-05s
Believability | Calculation of trust value for LinkedStats took 7.62939453125e-06s
INFO | --- Analysis for linkedstats took 3.8656322956085205s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.267692565917969e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.26460742950439453s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.0994415283203125e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 1.1920928955078125e-05s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.9734041690826416s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.1961669921875e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.28217220306396484s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.218650817871094e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 8.58306884765625e-06s
INFO | --- Analysis for linking-open-drug-data took 3.533637523651123s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.061508893966674805s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.26788330078125s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010967254638671875s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 6.9141387939453125e-06s
INFO | --- Analysis for linklion took 2.5358781814575195s
Availability | SPARQL endpoint availability check for Lion's Den took 4.4345855712890625e-05s
Availability | VoID file availability check for Lion's Den took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.2607545852661133s
Reputation | Calculation of the PageRank for Lion's Den took 0.020263195037841797s
Interlinking | Calculation of Degree of Connection for Lion's Den took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 2.86102294921875e-05s
Believability | Calculation of trust value for Lion's Den took 8.106231689453125e-06s
INFO | --- Analysis for lionsden took 2.9467222690582275s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 37.87183594703674s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.000804901123046875s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2426283359527588s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020398855209350586s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 4.887580871582031e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 48.20649433135986s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.744529724121094e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.2777717113494873s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 7.867813110351562e-06s
INFO | --- Analysis for livtdm took 2.909608840942383s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.1484832763671875e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.2565481662750244s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.9802322387695312e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 1.2636184692382812e-05s
INFO | --- Analysis for livtdm2017 took 3.027968645095825s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.2578163146972656s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 7.3909759521484375e-06s
INFO | --- Analysis for lobi took 2.943474769592285s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.2160027027130127s
Availability | VoID file availability check for lobid-organisations took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.3183436393737793s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02027440071105957s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.441375732421875e-05s
Believability | Calculation of trust value for lobid-organisations took 9.059906005859375e-06s
INFO | --- Analysis for lobid-organisations took 5.967817544937134s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.8719573020935059s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.2658348083496094s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010347366333007812s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 7.152557373046875e-06s
INFO | --- Analysis for lobid-resources took 8.191949605941772s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Open Colors took 0.001199483871459961s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2599911689758301s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020460128784179688s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0008196830749511719s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.534027099609375e-05s
Believability | Calculation of trust value for Linked Open Colors took 6.67572021484375e-06s
INFO | --- Analysis for loc took 7.219016075134277s
Availability | SPARQL endpoint availability check for Location Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Location Ontology took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.2560892105102539s
Reputation | Calculation of the PageRank for Location Ontology took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.8133392333984375e-05s
Believability | Calculation of trust value for Location Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for Location_Ontology took 3.453495740890503s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.2768888473510742s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 2.8848648071289062e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 6.9141387939453125e-06s
INFO | --- Analysis for locv took 22.720463514328003s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7375776767730713s
Availability | VoID file availability check for LOD-a-lot took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2677187919616699s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.218650817871094e-05s
Believability | Calculation of trust value for LOD-a-lot took 7.152557373046875e-06s
INFO | --- Analysis for lod-a-lot took 13.902355432510376s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.315376281738281e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.26085376739501953s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 7.3909759521484375e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.895002603530884s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 5.173683166503906e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.23599934577941895s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.021174192428588867s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.0994415283203125e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 6.67572021484375e-06s
INFO | --- Analysis for lod-taiwan took 3.057694435119629s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.291534423828125e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2525973320007324s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.535385131835938e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 6.9141387939453125e-06s
INFO | --- Analysis for lod2-project-wiki took 3.667074203491211s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.644388437271118s
Availability | VoID file availability check for LODAC BDLS took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.26008176803588867s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020267248153686523s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.796287536621094e-05s
Believability | Calculation of trust value for LODAC BDLS took 7.152557373046875e-06s
INFO | --- Analysis for lodac-bdls took 13.795584678649902s
Availability | SPARQL endpoint availability check for LODRussia Math took 5.7220458984375e-05s
Availability | VoID file availability check for LODRussia Math took 0.0004076957702636719s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2846944332122803s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 3.123283386230469e-05s
Believability | Calculation of trust value for LODRussia Math took 7.152557373046875e-06s
INFO | --- Analysis for lodrussia-math took 2.909959316253662s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.172325134277344e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.2507297992706299s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0008974075317382812s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.2901763916015625e-05s
Believability | Calculation of trust value for LODRussia Nano took 3.24249267578125e-05s
INFO | --- Analysis for lodrussia-nano took 2.8231570720672607s
Availability | SPARQL endpoint availability check for LODStats took 4.506111145019531e-05s
Availability | VoID file availability check for LODStats took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for LODStats took 0.2732882499694824s
Reputation | Calculation of the PageRank for LODStats took 0.020467758178710938s
Interlinking | Calculation of Degree of Connection for LODStats took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for LODStats took 2.9087066650390625e-05s
Believability | Calculation of trust value for LODStats took 7.867813110351562e-06s
INFO | --- Analysis for lodstats took 2.8469462394714355s
Availability | SPARQL endpoint availability check for LODUM took 4.100799560546875e-05s
Availability | VoID file availability check for LODUM took 0.000244140625s
Completeness | Calculation of interlinking completeness for LODUM took 0.2590169906616211s
Reputation | Calculation of the PageRank for LODUM took 0.02026820182800293s
Interlinking | Calculation of Degree of Connection for LODUM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for LODUM took 2.8133392333984375e-05s
Believability | Calculation of trust value for LODUM took 7.62939453125e-06s
INFO | --- Analysis for lodum took 2.912811517715454s
Availability | SPARQL endpoint availability check for lofd took 0.12347531318664551s
Availability | VoID file availability check for lofd took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for lofd took 0.27406764030456543s
Reputation | Calculation of the PageRank for lofd took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for lofd took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for lofd took 2.86102294921875e-05s
Believability | Calculation of trust value for lofd took 6.67572021484375e-06s
INFO | --- Analysis for lofd took 2.4120309352874756s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 270.85682916641235s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.3614654541015625s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 4.887580871582031e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 5.0067901611328125e-06s
INFO | --- Analysis for loius took 584.9747498035431s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.863739013671875e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.2919764518737793s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 3.62396240234375e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 7.867813110351562e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 4.441303968429565s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.8048107624053955s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.265455961227417s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020734310150146484s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.245208740234375e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.0067901611328125e-06s
INFO | --- Analysis for london-gazette took 4.18173623085022s
Availability | SPARQL endpoint availability check for Weather Stations took 4.553794860839844e-05s
Availability | VoID file availability check for Weather Stations took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.26960158348083496s
Reputation | Calculation of the PageRank for Weather Stations took 0.020801782608032227s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 9.083747863769531e-05s
Believability | Calculation of trust value for Weather Stations took 7.867813110351562e-06s
INFO | --- Analysis for los_metar took 82.95162749290466s
Availability | SPARQL endpoint availability check for Lotico took 0.9249303340911865s
Availability | VoID file availability check for Lotico took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Lotico took 0.280437707901001s
Reputation | Calculation of the PageRank for Lotico took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Lotico took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.20159912109375e-05s
Believability | Calculation of trust value for Lotico took 7.867813110351562e-06s
INFO | --- Analysis for lotico took 7.789752006530762s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 1.1183230876922607s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.25142478942871094s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.0994415283203125e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 7.3909759521484375e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 7.682199001312256s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.0356805324554443s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0002636909484863281s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 128.59121775627136s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9712903499603271s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.855077266693115s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 15.884154796600342s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.16471767425537s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.2444770336151123s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.25734496116638184s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.53553056716919s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.24310684204101562s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4238722324371338s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2090759277344s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.28254055976867676s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.015515089035034s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8432180881500244s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4376082420349121s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19967389106750488s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.26360559463500977s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.15775442123413s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0001049041748046875s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2096691131591797s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2149972915649414s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4644780158996582s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4443678855895996s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.5535666942596436s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5123825073242188s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2283332347869873s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 149.64058470726013s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6464462280273438e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19599223136901855s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3708229064941406s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.34114623069763184s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 44.92509317398071s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6569604873657227s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7336623668670654s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1770625114440918s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 90.14975142478943s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.438623189926147s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 37.377851486206055s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3749210834503174s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 84.61857485771179s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7518253326416016s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5726902484893799s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.703040599822998s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.301788806915283s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3877816200256348s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.021169424057006836s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0008993148803710938s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for LPIS_(Poland) took 2293.46116399765s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19252896308898926s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.000308990478515625s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 117.93253207206726s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.992436408996582s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.517030954360962s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 15.564453840255737s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.23192954063416s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.2602665424346924s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2489304542541504s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.193256855010986s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2796180248260498s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.47823357582092285s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.19218707084656s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2890133857727051s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7994163036346436s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.726980447769165s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3006148338317871s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2019946575164795s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2762906551361084s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.437307119369507s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.128715515136719e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20116567611694336s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19808602333068848s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4660048484802246s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4283328056335449s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.7485740184783936s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4671154022216797s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2375931739807129s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 155.61714625358582s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18315577507019043s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3544604778289795s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3548126220703125s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 43.88046360015869s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6818645000457764s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6669914722442627s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18270564079284668s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 82.02043604850769s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.447758436203003s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 48.26225256919861s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.362105369567871s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 82.3487319946289s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.828451633453369s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.636847734451294s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.6780557632446289s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.814778804779053s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9647419452667236s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.02113795280456543s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.0067901611328125e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 2274.0003702640533s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.57763671875e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.2720177173614502s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020859956741333008s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.0994415283203125e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 7.867813110351562e-06s
INFO | --- Analysis for lremap-auth took 28.439743757247925s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 5.173683166503906e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2630302906036377s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02404952049255371s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.647804260253906e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 7.152557373046875e-06s
INFO | --- Analysis for lremap-conf took 15.80106806755066s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.506111145019531e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.6877553462982178s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.123283386230469e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 7.867813110351562e-06s
INFO | --- Analysis for lremap-ri took 15.394005060195923s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.363059997558594e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.27061915397644043s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.0040740966796875e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.33514404296875e-05s
INFO | --- Analysis for lremap-sub took 15.256037473678589s
Availability | SPARQL endpoint availability check for LSQ took 4.3392181396484375e-05s
Availability | VoID file availability check for LSQ took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for LSQ took 0.26810288429260254s
Reputation | Calculation of the PageRank for LSQ took 0.021762609481811523s
Interlinking | Calculation of Degree of Connection for LSQ took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.266334533691406e-05s
Believability | Calculation of trust value for LSQ took 6.4373016357421875e-06s
INFO | --- Analysis for lsq took 3.4426984786987305s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 180.48969101905823s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0003559589385986328s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.2616095542907715s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020327329635620117s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for LucaniPharsalia took 314.88091564178467s
Availability | SPARQL endpoint availability check for Linked rules took 0.00010204315185546875s
Availability | VoID file availability check for Linked rules took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2599918842315674s
Reputation | Calculation of the PageRank for Linked rules took 0.02335810661315918s
Interlinking | Calculation of Degree of Connection for Linked rules took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked rules took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Linked rules took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked rules took 6.9141387939453125e-06s
INFO | --- Analysis for Luminaires_senlis took 2.5546140670776367s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.291534423828125e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.27639150619506836s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.1948089599609375e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 2.5987625122070312e-05s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 3.8187146186828613s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.14308190345764s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.6859145164489746s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0008726119995117188s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 4.267692565917969e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 6.9141387939453125e-06s
INFO | --- Analysis for makg took 123.98633766174316s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.315376281738281e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.00032401084899902344s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.2419438362121582s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.600120544433594e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 9.059906005859375e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.301032066345215s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.38690185546875e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.263277530670166s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.765655517578125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.62939453125e-06s
INFO | --- Analysis for manish took 2.324331283569336s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00012969970703125s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.2826664447784424s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.8848648071289062e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 7.3909759521484375e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.99861216545105s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.220008850097656e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.26741552352905273s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 2.7418136596679688e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 7.867813110351562e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.8947036266326904s
Availability | SPARQL endpoint availability check for MARC Codes List took 6.794929504394531e-05s
Availability | VoID file availability check for MARC Codes List took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.25169849395751953s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012540817260742188s
Believability | Calculation of trust value for MARC Codes List took 6.4373016357421875e-06s
INFO | --- Analysis for marc-codes took 13.794259548187256s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.315376281738281e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.28045010566711426s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.076957702636719e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 5.7220458984375e-06s
INFO | --- Analysis for masc took 5.9144606590271s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.220008850097656e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2720000743865967s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.743171691894531e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 6.9141387939453125e-06s
INFO | --- Analysis for masc-bn-nif took 2.4911677837371826s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.4776802062988281s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2837855815887451s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.0994415283203125e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 8.58306884765625e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 3.9668948650360107s
Availability | SPARQL endpoint availability check for medline took 4.220008850097656e-05s
Availability | VoID file availability check for medline took 0.00033593177795410156s
Completeness | Calculation of interlinking completeness for medline took 0.3311638832092285s
Reputation | Calculation of the PageRank for medline took 0.020274877548217773s
Interlinking | Calculation of Degree of Connection for medline took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for medline took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for medline took 3.314018249511719e-05s
Believability | Calculation of trust value for medline took 6.4373016357421875e-06s
INFO | --- Analysis for medline took 7.20958137512207s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 2.3162314891815186s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.2876157760620117s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.914138793945312e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 7.62939453125e-06s
INFO | --- Analysis for meducator took 14.008577108383179s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.076957702636719e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2445080280303955s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 3.0040740966796875e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 7.3909759521484375e-06s
INFO | --- Analysis for mesh-finnish took 2.7692086696624756s
Availability | SPARQL endpoint availability check for MeSH headings took 4.3392181396484375e-05s
Availability | VoID file availability check for MeSH headings took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.2676839828491211s
Reputation | Calculation of the PageRank for MeSH headings took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.9802322387695312e-05s
Believability | Calculation of trust value for MeSH headings took 6.9141387939453125e-06s
INFO | --- Analysis for mesh_headings took 2.9354121685028076s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.220008850097656e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2505033016204834s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.0204312801361084s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.0994415283203125e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 7.62939453125e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.9208714962005615s
Availability | SPARQL endpoint availability check for MeSH pairs took 5.125999450683594e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002994537353515625s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2423100471496582s
Reputation | Calculation of the PageRank for MeSH pairs took 0.021190166473388672s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.9087066650390625e-05s
Believability | Calculation of trust value for MeSH pairs took 7.152557373046875e-06s
INFO | --- Analysis for mesh_pairs took 2.886685371398926s
Availability | SPARQL endpoint availability check for MeSH titles took 4.172325134277344e-05s
Availability | VoID file availability check for MeSH titles took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.2746109962463379s
Reputation | Calculation of the PageRank for MeSH titles took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for MeSH titles took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 2.86102294921875e-05s
Believability | Calculation of trust value for MeSH titles took 7.867813110351562e-06s
INFO | --- Analysis for mesh_titles took 2.9841396808624268s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.315376281738281e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0003273487091064453s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.25522351264953613s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 2.86102294921875e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 6.9141387939453125e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.8784430027008057s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.506111145019531e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.28248095512390137s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 2.7894973754882812e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 7.867813110351562e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.895864963531494s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.38690185546875e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.28042149543762207s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.176399230957031e-05s
Believability | Calculation of trust value for MetaShare metadata model took 7.62939453125e-06s
INFO | --- Analysis for metashare took 2.5589663982391357s
Availability | SPARQL endpoint availability check for MExiCo took 4.696846008300781e-05s
Availability | VoID file availability check for MExiCo took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for MExiCo took 0.27561068534851074s
Reputation | Calculation of the PageRank for MExiCo took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.935264587402344e-05s
Believability | Calculation of trust value for MExiCo took 7.152557373046875e-06s
INFO | --- Analysis for mexico took 22.489610195159912s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0390605926513672s
Availability | VoID file availability check for Coronavirus dataset took 0.0002810955047607422s
Extra | Recovery of all triples for Coronavirus dataset took 10.723523378372192s
Performance | Total latancy measurement for Coronavirus dataset took 2.4848287105560303s
Amount of data | Number of triples check for Coronavirus dataset took 1.2057764530181885s
Interoperability | New terms check for Coronavirus dataset took 2.5245940685272217s
Versatility | Languages check for Coronavirus dataset took 60.516467809677124s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.5132410526275635s
Interpretability | RDF structures check for Coronavirus dataset took 0.5265965461730957s
Versatility | Serialization formats check for Coronavirus dataset took 0.5509920120239258s
Availability | RDF dump link check for Coronavirus dataset took 0.4906919002532959s
License | MR license check for Coronavirus dataset took 0.5506305694580078s
License | HR license check for Coronavirus dataset took 42.561949253082275s
Amount of data | Number of property check for Coronavirus dataset took 0.5346152782440186s
Understandability | Number of label check for Coronavirus dataset took 1.5308294296264648s
Understandability | URI regex check for Coronavirus dataset took 1.0023837089538574s
Understandability | Vocabs check for Coronavirus dataset took 0.4897584915161133s
Verifiability | Authors check for Coronavirus dataset took 0.5248572826385498s
Verifiability | Publishers check for Coronavirus dataset took 0.49676966667175293s
Performance | Throughput check for Coronavirus dataset took 14.203575134277344s
Amount of data | Check the number of entities for Coronavirus dataset took 7.43865966796875e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.49025964736938477s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5370516777038574s
Interlinking | skos check for Coronavirus dataset took 0.5439615249633789s
Interlinking | skos check for Coronavirus dataset took 0.491344690322876s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.510810375213623s
Currency | Creation date check for Coronavirus dataset took 1.0298151969909668s
Currency | Modification date check for Coronavirus dataset took 1.0175378322601318s
Rep.Conc. | URIs length for Coronavirus dataset took 9.019011497497559s
Interoperability | New vocabularies check for Coronavirus dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5158958435058594s
Accuracy | Check Functional Property for Coronavirus dataset took 0.5820508003234863s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.726393461227417s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.3494210243225098s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022800445556640625s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.02843618392944336s
Consistency | Disjoint class check for Coronavirus dataset took 1.1077513694763184s
Consistency | Check Misplaced properties for Coronavirus dataset took 8.238029956817627s
Consistency | Misplaced classes for Coronavirus dataset took 0.6178488731384277s
Consistency | Check Ontology hijacking for Coronavirus dataset took 4.044057846069336s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.290940761566162s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 7.168191194534302s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.0356755256652832s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.546299934387207s
Security | Sign check for Coronavirus dataset took 0.5371308326721191s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3109.463907957077s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.1816706657409668s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.02095317840576172s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 5.91278076171875e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 7.3909759521484375e-06s
INFO | --- Analysis for micro-coronavirus took 3350.8766984939575s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 5.2928924560546875e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.28138089179992676s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.019870996475219727s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010609626770019531s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 6.598051071166992s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.458427429199219e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.24891042709350586s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011396408081054688s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for mismuseos-gnoss took 8.503998517990112s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.10497736930847168s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.25376248359680176s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020315170288085938s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.267692565917969e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.152557373046875e-06s
INFO | --- Analysis for mlsa took 3.5226659774780273s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.3392181396484375e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2677328586578369s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020933151245117188s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.147125244140625e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 7.62939453125e-06s
INFO | --- Analysis for model took 35.80054688453674s
Availability | SPARQL endpoint availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 4.315376281738281e-05s
Availability | VoID file availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.27387166023254395s
Reputation | Calculation of the PageRank for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 3.600120544433594e-05s
Believability | Calculation of trust value for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 8.106231689453125e-06s
INFO | --- Analysis for model1 took 23.360803842544556s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.076957702636719e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.25278162956237793s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 3.0279159545898438e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 7.867813110351562e-06s
INFO | --- Analysis for mond took 3.9186296463012695s
Availability | SPARQL endpoint availability check for MONDIS took 4.267692565917969e-05s
Availability | VoID file availability check for MONDIS took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for MONDIS took 0.28499865531921387s
Reputation | Calculation of the PageRank for MONDIS took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for MONDIS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MONDIS took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.9802322387695312e-05s
Believability | Calculation of trust value for MONDIS took 9.298324584960938e-06s
INFO | --- Analysis for mondis took 4.7181010246276855s
Availability | SPARQL endpoint availability check for Monumentos took 4.1484832763671875e-05s
Availability | VoID file availability check for Monumentos took 0.0003635883331298828s
Completeness | Calculation of interlinking completeness for Monumentos took 0.25378847122192383s
Reputation | Calculation of the PageRank for Monumentos took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.1948089599609375e-05s
Believability | Calculation of trust value for Monumentos took 8.106231689453125e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.9060213565826416s
Availability | SPARQL endpoint availability check for MORElab took 1.7316009998321533s
Availability | VoID file availability check for MORElab took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for MORElab took 0.26711201667785645s
Reputation | Calculation of the PageRank for MORElab took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for MORElab took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.630752563476562e-05s
Believability | Calculation of trust value for MORElab took 7.3909759521484375e-06s
INFO | --- Analysis for morelab took 5.55129861831665s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.060546398162842s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.24753093719482422s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02010822296142578s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.606910705566406e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.2159347534179688e-05s
INFO | --- Analysis for msc took 6.506100416183472s
Availability | SPARQL endpoint availability check for Multext-East took 4.1961669921875e-05s
Availability | VoID file availability check for Multext-East took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Multext-East took 0.26706647872924805s
Reputation | Calculation of the PageRank for Multext-East took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.123283386230469e-05s
Believability | Calculation of trust value for Multext-East took 6.67572021484375e-06s
INFO | --- Analysis for multext-east took 2.4091076850891113s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.1484832763671875e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.29929280281066895s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 2.6702880859375e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.059906005859375e-06s
INFO | --- Analysis for multilingualeulaw took 2.9844353199005127s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.482269287109375e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2820453643798828s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.409385681152344e-05s
Believability | Calculation of trust value for Multimedia Lab took 6.9141387939453125e-06s
INFO | --- Analysis for multimedia-lab took 2.5190868377685547s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.100799560546875e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.26401400566101074s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 2.9087066650390625e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 7.152557373046875e-06s
INFO | --- Analysis for munich-offener-haushalt took 2.9734222888946533s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.6802887916564941s
Availability | VoID file availability check for Muninn World War I took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.26804542541503906s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.153915405273438e-05s
Believability | Calculation of trust value for Muninn World War I took 7.3909759521484375e-06s
INFO | --- Analysis for muninn-world-war-i took 10.885998249053955s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.792213439941406e-05s
Availability | VoID file availability check for Musei Italiani took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.2630176544189453s
Reputation | Calculation of the PageRank for Musei Italiani took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 2.9802322387695312e-05s
Believability | Calculation of trust value for Musei Italiani took 7.152557373046875e-06s
INFO | --- Analysis for musei-italiani took 2.8437323570251465s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 5.054473876953125e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.28400611877441406s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010943412780761719s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for museosespania-gnoss took 81.3743827342987s
Availability | SPARQL endpoint availability check for Italian Museums took 1.8758301734924316s
Availability | VoID file availability check for Italian Museums took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.2546656131744385s
Reputation | Calculation of the PageRank for Italian Museums took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for Italian Museums took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.225440979003906e-05s
Believability | Calculation of trust value for Italian Museums took 7.3909759521484375e-06s
INFO | --- Analysis for museums-in-italy took 4.381114959716797s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.601478576660156e-05s
Availability | VoID file availability check for MusicBrainz took 0.0003788471221923828s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.2650332450866699s
Reputation | Calculation of the PageRank for MusicBrainz took 0.0207977294921875s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.314018249511719e-05s
Believability | Calculation of trust value for MusicBrainz took 7.3909759521484375e-06s
INFO | --- Analysis for musicbrainz_ took 3.1325747966766357s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.1961669921875e-05s
Availability | VoID file availability check for MusicNet Codex took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.268632173538208s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.7894973754882812e-05s
Believability | Calculation of trust value for MusicNet Codex took 7.62939453125e-06s
INFO | --- Analysis for musicnet_codex took 2.986316680908203s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7471592426300049s
Availability | VoID file availability check for Muziekweb took 0.0005581378936767578s
Extra | Recovery of all triples for Muziekweb took 1.9723803997039795s
Performance | Total latancy measurement for Muziekweb took 1.353081464767456s
Amount of data | Number of triples check for Muziekweb took 0.37834739685058594s
Interoperability | New terms check for Muziekweb took 1.6708805561065674s
Versatility | Languages check for Muziekweb took 53.41713190078735s
Interpretability | Number of blank nodes check for Muziekweb took 0.33415889739990234s
Interpretability | RDF structures check for Muziekweb took 0.4988529682159424s
Versatility | Serialization formats check for Muziekweb took 0.3060495853424072s
Availability | RDF dump link check for Muziekweb took 0.27819204330444336s
License | MR license check for Muziekweb took 0.3120596408843994s
License | HR license check for Muziekweb took 11.553757190704346s
Amount of data | Number of property check for Muziekweb took 0.3069775104522705s
Understandability | Number of label check for Muziekweb took 0.3461117744445801s
Understandability | URI regex check for Muziekweb took 0.5607335567474365s
Understandability | Vocabs check for Muziekweb took 0.29457688331604004s
Verifiability | Authors check for Muziekweb took 0.31912708282470703s
Verifiability | Publishers check for Muziekweb took 0.28202223777770996s
Performance | Throughput check for Muziekweb took 11.689659833908081s
Amount of data | Check the number of entities for Muziekweb took 7.104873657226562e-05s
Verifiability | Contribs. check for Muziekweb took 0.3189046382904053s
Interlinking | sameAs chians check for Muziekweb took 0.2804133892059326s
Interlinking | skos check for Muziekweb took 0.3452014923095703s
Interlinking | skos check for Muziekweb took 0.2905845642089844s
Timeliness | dataset update frequency check for Muziekweb took 0.3076157569885254s
Currency | Creation date check for Muziekweb took 0.8192024230957031s
Currency | Modification date check for Muziekweb took 0.7258219718933105s
Rep.Conc. | URIs length for Muziekweb took 1.9855809211730957s
Interoperability | New vocabularies check for Muziekweb took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.26762962341308594s
Accuracy | Check Functional Property for Muziekweb took 0.4505007266998291s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.4918532371520996s
Accuracy | Check Empty annotation labels for Muziekweb took 0.9226408004760742s
Accuracy | Check White space in annotation for Muziekweb took 0.0281069278717041s
Accuracy | Check Datatype consistency for Muziekweb took 0.028539657592773438s
Consistency | Disjoint class check for Muziekweb took 0.48067164421081543s
Consistency | Check Misplaced properties for Muziekweb took 1.114928960800171s
Consistency | Check Ontology hijacking for Muziekweb took 2.190183401107788s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.2643048763275146s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.5373549461364746s
Conciseness | Check Extensional conciseness for Muziekweb took 0.033402442932128906s
Conciseness | Check Intensional conciseness for Muziekweb took 0.29963231086730957s
Security | Sign check for Muziekweb took 0.3091874122619629s
Availability | Check URIs Dereferenciability for Muziekweb took 1768.4051930904388s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.5198066234588623s
Reputation | Calculation of the PageRank for Muziekweb took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 5.8650970458984375e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 2.6226043701171875e-06s
Believability | Calculation of trust value for Muziekweb took 7.62939453125e-06s
INFO | --- Analysis for muziekweb took 1893.9585461616516s
Availability | SPARQL endpoint availability check for myExperiment took 0.31066203117370605s
Availability | VoID file availability check for myExperiment took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for myExperiment took 0.30094146728515625s
Reputation | Calculation of the PageRank for myExperiment took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for myExperiment took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for myExperiment took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010561943054199219s
Believability | Calculation of trust value for myExperiment took 9.298324584960938e-06s
INFO | --- Analysis for my-experiment took 4.547483921051025s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.09166812896728516s
Availability | VoID file availability check for My Family Lineage took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.2968473434448242s
Reputation | Calculation of the PageRank for My Family Lineage took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0009644031524658203s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 9.918212890625e-05s
Believability | Calculation of trust value for My Family Lineage took 7.152557373046875e-06s
INFO | --- Analysis for my-family-lineage took 5.110874652862549s
Availability | SPARQL endpoint availability check for My ontology test took 0.3990919589996338s
Availability | VoID file availability check for My ontology test took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for My ontology test took 0.2579796314239502s
Reputation | Calculation of the PageRank for My ontology test took 0.020519256591796875s
Interlinking | Calculation of Degree of Connection for My ontology test took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for My ontology test took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for My ontology test took 2.8371810913085938e-05s
Believability | Calculation of trust value for My ontology test took 8.344650268554688e-06s
INFO | --- Analysis for myontologytest took 3.1426432132720947s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.363059997558594e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.3094959259033203s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00010132789611816406s
Believability | Calculation of trust value for myopenlink dataspaces took 6.9141387939453125e-06s
INFO | --- Analysis for myopenlink-dataspaces took 2.8015551567077637s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 4.406176567077637s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.255110502243042s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02013850212097168s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.200241088867188e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 12.094220161437988s
Availability | SPARQL endpoint availability check for NAICS 2007 took 25.95183753967285s
Availability | VoID file availability check for NAICS 2007 took 0.0009818077087402344s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.2883296012878418s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.02178192138671875s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0008647441864013672s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.792213439941406e-05s
Believability | Calculation of trust value for NAICS 2007 took 6.67572021484375e-06s
INFO | --- Analysis for naics-2007 took 125.53825950622559s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.362837314605713s
Availability | VoID file availability check for NAICS 2012 took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.27382612228393555s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.02090311050415039s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0008981227874755859s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 4.982948303222656e-05s
Believability | Calculation of trust value for NAICS 2012 took 4.76837158203125e-06s
INFO | --- Analysis for naics-2012 took 125.24305963516235s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.32184672355651855s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0008900165557861328s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.412101745605469e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for nalt took 6.594187021255493s
Availability | SPARQL endpoint availability check for Usernames  took 4.3392181396484375e-05s
Availability | VoID file availability check for Usernames  took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Usernames  took 0.3298022747039795s
Reputation | Calculation of the PageRank for Usernames  took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for Usernames  took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Usernames  took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.0040740966796875e-05s
Believability | Calculation of trust value for Usernames  took 8.106231689453125e-06s
INFO | --- Analysis for Names took 5.7775561809539795s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.3491344451904297s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007195472717285156s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.0244677066802979s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.9285454750061035s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.624727487564087s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 28.179258584976196s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.3328099250793457s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.883958578109741s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.8673841953277588s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.4010739326477051s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.42810583114624023s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.39989280700683594s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.40929436683654785s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.82846593856812s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.9989023208618164s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 7.830162763595581s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7485888004302979s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.4243781566619873s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.3760383129119873s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.4037611484527588s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.754972219467163s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 9.72747802734375e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.3720264434814453s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.6157042980194092s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 2.045437812805176s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.1452105045318604s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.404280424118042s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1160979270935059s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7817118167877197s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.021305799484253s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.35987305641174316s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.4115738868713379s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.4180328845977783s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.41424012184143066s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007734298706054688s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0009891986846923828s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.39043354988098145s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7421531677246094s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.41657376289367676s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.6661114692687988s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.2793796062469482s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.6438572406768799s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0005908012390136719s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.33641862869262695s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 3.6092207431793213s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.2749624252319336s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 5.0067901611328125e-06s
INFO | --- Analysis for national-diet-library-authorities took 242.6800353527069s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.4238269329071045s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005533695220947266s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 0.824669599533081s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 2.035912036895752s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.819953918457031s
Interoperability | New terms check for National Diet Library of Japan subject headings took 24.018707752227783s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.386807918548584s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 14.255395650863647s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.38485026359558105s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3732411861419678s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.32761240005493164s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.39626169204711914s
License | MR license check for National Diet Library of Japan subject headings took 0.4344639778137207s
License | HR license check for National Diet Library of Japan subject headings took 91.82719945907593s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.877471923828125s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.714273452758789s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.817974328994751s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.385974645614624s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3610973358154297s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.38465070724487305s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.58039379119873s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 3.886222839355469e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.34499359130859375s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.5263748168945312s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.5975086688995361s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.4037830829620361s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.334273099899292s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.1516497135162354s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.760042667388916s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 1.0403552055358887s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.3595235347747803s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.4090125560760498s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.35098934173583984s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.3508923053741455s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007526874542236328s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0009894371032714844s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.346691370010376s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7123057842254639s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.37959909439086914s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.6326663494110107s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.2721717357635498s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.6480438709259033s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0005819797515869141s
Security | Sign check for National Diet Library of Japan subject headings took 0.40502500534057617s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 3.710012674331665s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.34954166412353516s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 6.198883056640625e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 233.5145800113678s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.8734149932861328s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0003333091735839844s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.2787439823150635s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02046799659729004s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.172325134277344e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 7.867813110351562e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.979309558868408s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.3392181396484375e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.26514649391174316s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.2479248046875e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.867813110351562e-06s
INFO | --- Analysis for Naturopathy took 3.8864455223083496s
Availability | SPARQL endpoint availability check for Naturopathy took 6.67572021484375e-05s
Availability | VoID file availability check for Naturopathy took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.25926876068115234s
Reputation | Calculation of the PageRank for Naturopathy took 0.020506620407104492s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 2.8371810913085938e-05s
Believability | Calculation of trust value for Naturopathy took 7.3909759521484375e-06s
INFO | --- Analysis for naturopathy2 took 3.3559951782226562s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.2767207622528076s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02032780647277832s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for NCI Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for nci-thesaurus took 2.9904403686523438s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.3990066051483154s
Availability | VoID file availability check for COVID-19 Data took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.27553462982177734s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for COVID-19 Data took 6.9141387939453125e-06s
INFO | --- Analysis for NCMI-COVID-19 took 7.209995269775391s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.406520128250122s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.26820945739746094s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020506620407104492s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2636184692382812e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 7.867813110351562e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.1396543979644775s
Availability | SPARQL endpoint availability check for NDF-RT took 4.410743713378906e-05s
Availability | VoID file availability check for NDF-RT took 0.0007512569427490234s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.27097320556640625s
Reputation | Calculation of the PageRank for NDF-RT took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for NDF-RT took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 2.86102294921875e-05s
Believability | Calculation of trust value for NDF-RT took 1.2636184692382812e-05s
INFO | --- Analysis for ndf-rt took 2.946793556213379s
Availability | SPARQL endpoint availability check for Near took 4.315376281738281e-05s
Availability | VoID file availability check for Near took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for Near took 0.29645347595214844s
Reputation | Calculation of the PageRank for Near took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for Near took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Near took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Near took 9.441375732421875e-05s
Believability | Calculation of trust value for Near took 7.867813110351562e-06s
INFO | --- Analysis for near took 9.596259593963623s
Availability | SPARQL endpoint availability check for Neel took 4.100799560546875e-05s
Availability | VoID file availability check for Neel took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Neel took 0.2623405456542969s
Reputation | Calculation of the PageRank for Neel took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for Neel took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neel took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Neel took 2.8848648071289062e-05s
Believability | Calculation of trust value for Neel took 7.62939453125e-06s
INFO | --- Analysis for neel took 2.894965648651123s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.649162292480469e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.28029513359069824s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 2.9802322387695312e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 8.344650268554688e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.908886194229126s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.363059997558594e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2554633617401123s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.0213925838470459s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.001323699951171875s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 5.1021575927734375e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 7.867813110351562e-06s
INFO | --- Analysis for neurolex-wiki took 2.6200575828552246s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.3392181396484375e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.26938772201538086s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020790576934814453s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.458427429199219e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 7.3909759521484375e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.4261062145233154s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.29328417778015137s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 7.367134094238281e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 7.152557373046875e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.199585914611816s
Availability | SPARQL endpoint availability check for Newsweek took 7.2479248046875e-05s
Availability | VoID file availability check for Newsweek took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Newsweek took 0.2515897750854492s
Reputation | Calculation of the PageRank for Newsweek took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Newsweek took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Newsweek took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.0517578125e-05s
Believability | Calculation of trust value for Newsweek took 8.106231689453125e-06s
INFO | --- Analysis for newsweek took 2.941720485687256s
Availability | SPARQL endpoint availability check for neXtProt took 1.4430105686187744s
Availability | VoID file availability check for neXtProt took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2464916706085205s
Reputation | Calculation of the PageRank for neXtProt took 0.021253347396850586s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0009410381317138672s
Interlinking | Calculation of Clustering coefficient for neXtProt took 4.076957702636719e-05s
Believability | Calculation of trust value for neXtProt took 8.344650268554688e-06s
INFO | --- Analysis for nextprot took 4.543870687484741s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.9591064453125e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2604086399078369s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.000102996826171875s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for nextweb-gnoss took 9.615071773529053s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.291534423828125e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.3188631534576416s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 7.867813110351562e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 4.76837158203125e-06s
INFO | --- Analysis for nhs-jargon took 2.9451816082000732s
Availability | SPARQL endpoint availability check for NIT Patna took 4.315376281738281e-05s
Availability | VoID file availability check for NIT Patna took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.2658224105834961s
Reputation | Calculation of the PageRank for NIT Patna took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for NIT Patna took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.604194641113281e-05s
Believability | Calculation of trust value for NIT Patna took 6.9141387939453125e-06s
INFO | --- Analysis for NITP took 3.377797842025757s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.100799560546875e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.2675905227661133s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.2901763916015625e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 8.106231689453125e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.8973326683044434s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.26848602294921875s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 6.67572021484375e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.258875846862793s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.5227079391479492s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.26303887367248535s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for NLW took 4.074052333831787s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.4620254039764404s
Availability | VoID file availability check for Nobel Prizes took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.29029130935668945s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02020883560180664s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.107589721679688e-05s
Believability | Calculation of trust value for Nobel Prizes took 6.9141387939453125e-06s
INFO | --- Analysis for nobelprizes took 8.525995969772339s
Availability | SPARQL endpoint availability check for NoiPA took 0.2970578670501709s
Availability | VoID file availability check for NoiPA took 0.000255584716796875s
Extra | Recovery of all triples for NoiPA took 83.10218596458435s
Performance | Total latancy measurement for NoiPA took 0.9738919734954834s
Amount of data | Number of triples check for NoiPA took 1.621251106262207s
Interoperability | New terms check for NoiPA took 2.96044659614563s
Versatility | Languages check for NoiPA took 0.13898992538452148s
Interpretability | Number of blank nodes check for NoiPA took 0.2290956974029541s
Interpretability | RDF structures check for NoiPA took 0.22147440910339355s
Versatility | Serialization formats check for NoiPA took 0.18790793418884277s
Availability | RDF dump link check for NoiPA took 0.2652418613433838s
License | MR license check for NoiPA took 0.4203805923461914s
License | HR license check for NoiPA took 60.21192502975464s
Amount of data | Number of property check for NoiPA took 0.2662487030029297s
Understandability | Number of label check for NoiPA took 0.6122946739196777s
Understandability | URI regex check for NoiPA took 0.4629838466644287s
Understandability | Vocabs check for NoiPA took 0.3042278289794922s
Verifiability | Authors check for NoiPA took 0.18631792068481445s
Verifiability | Publishers check for NoiPA took 0.23009991645812988s
Performance | Throughput check for NoiPA took 10.99926495552063s
Amount of data | Check the number of entities for NoiPA took 5.0067901611328125e-05s
Verifiability | Contribs. check for NoiPA took 0.14870285987854004s
Interlinking | sameAs chians check for NoiPA took 0.10093879699707031s
Interlinking | skos check for NoiPA took 0.32498812675476074s
Interlinking | skos check for NoiPA took 0.1819915771484375s
Timeliness | dataset update frequency check for NoiPA took 0.15983152389526367s
Currency | Creation date check for NoiPA took 0.2838289737701416s
Currency | Modification date check for NoiPA took 0.14492440223693848s
Rep.Conc. | URIs length for NoiPA took 50.50159215927124s
Interoperability | New vocabularies check for NoiPA took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.22006702423095703s
Accuracy | Check Functional Property for NoiPA took 0.14594769477844238s
Accuracy | Check Inverse Functional Property for NoiPA took 0.28339648246765137s
Accuracy | Check Empty annotation labels for NoiPA took 25.03592848777771s
Accuracy | Check White space in annotation for NoiPA took 2.228874444961548s
Accuracy | Check Datatype consistency for NoiPA took 1.989297866821289s
Consistency | Disjoint class check for NoiPA took 0.26495909690856934s
Consistency | Check Misplaced properties for NoiPA took 18.775124311447144s
Consistency | Misplaced classes for NoiPA took 6.342992305755615s
Consistency | Check Ontology hijacking for NoiPA took 26.20253896713257s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.6880567073822021s
Consistency | Check Invalid usage of undefined properties for NoiPA took 19.473655700683594s
Conciseness | Check Extensional conciseness for NoiPA took 2.182389974594116s
Conciseness | Check Intensional conciseness for NoiPA took 0.24125933647155762s
Security | Sign check for NoiPA took 0.1206045150756836s
Availability | Check URIs Dereferenciability for NoiPA took 12.574323892593384s
Completeness | Calculation of interlinking completeness for NoiPA took 0.34130239486694336s
Reputation | Calculation of the PageRank for NoiPA took 0.02101731300354004s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.5762786865234375e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 2.1457672119140625e-06s
Believability | Calculation of trust value for NoiPA took 6.67572021484375e-06s
INFO | --- Analysis for NoiPA took 469.12761187553406s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 5.756953477859497s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0003466606140136719s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.24423694610595703s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 8.726119995117188e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 7.3909759521484375e-06s
INFO | --- Analysis for nom took 22.280497789382935s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 24.89784049987793s
Availability | VoID file availability check for Nomenclator Asturias took 0.0009126663208007812s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.39824652671813965s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.606910705566406e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.7220458984375e-06s
INFO | --- Analysis for nomenclator-asturias took 137.65407419204712s
Availability | SPARQL endpoint availability check for nomisma took 4.172325134277344e-05s
Availability | VoID file availability check for nomisma took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for nomisma took 0.28820276260375977s
Reputation | Calculation of the PageRank for nomisma took 0.021126508712768555s
Interlinking | Calculation of Degree of Connection for nomisma took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.6716461181640625e-05s
Believability | Calculation of trust value for nomisma took 8.106231689453125e-06s
INFO | --- Analysis for nomisma took 4.331162691116333s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.6776163578033447s
Availability | VoID file availability check for Nomisma.org  took 0.0006055831909179688s
Extra | Recovery of all triples for Nomisma.org  took 300.1040270328522s
Performance | Total latancy measurement for Nomisma.org  took 3.072540521621704s
Amount of data | Number of triples check for Nomisma.org  took 39.366100788116455s
Interoperability | New terms check for Nomisma.org  took 9.424197673797607s
Versatility | Languages check for Nomisma.org  took 108.38578724861145s
Interpretability | Number of blank nodes check for Nomisma.org  took 50.27972650527954s
Security | Check HTTPS for Nomisma.org  took 0.8827488422393799s
Interpretability | RDF structures check for Nomisma.org  took 0.4824347496032715s
Versatility | Serialization formats check for Nomisma.org  took 0.43393778800964355s
Availability | RDF dump link check for Nomisma.org  took 913.3312594890594s
License | MR license check for Nomisma.org  took 0.5479495525360107s
License | HR license check for Nomisma.org  took 59.28630208969116s
Amount of data | Number of property check for Nomisma.org  took 0.43222713470458984s
Understandability | Number of label check for Nomisma.org  took 7.629776477813721s
Understandability | URI regex check for Nomisma.org  took 0.8645868301391602s
Understandability | Vocabs check for Nomisma.org  took 0.39008474349975586s
Verifiability | Authors check for Nomisma.org  took 0.3942263126373291s
Verifiability | Publishers check for Nomisma.org  took 0.43089890480041504s
Performance | Throughput check for Nomisma.org  took 12.063140630722046s
Amount of data | Check the number of entities for Nomisma.org  took 0.00038051605224609375s
Verifiability | Contribs. check for Nomisma.org  took 0.5395321846008301s
Interlinking | sameAs chians check for Nomisma.org  took 0.544532299041748s
Interlinking | skos check for Nomisma.org  took 1.7704663276672363s
Interlinking | skos check for Nomisma.org  took 0.5644567012786865s
Timeliness | dataset update frequency check for Nomisma.org  took 0.41489076614379883s
Currency | Creation date check for Nomisma.org  took 0.8629703521728516s
Currency | Modification date check for Nomisma.org  took 0.4686875343322754s
Rep.Conc. | URIs length for Nomisma.org  took 922.1865613460541s
Interoperability | New vocabularies check for Nomisma.org  took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.6724882125854492s
Accuracy | Check Functional Property for Nomisma.org  took 0.8273701667785645s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.405332088470459s
Accuracy | Check Empty annotation labels for Nomisma.org  took 615.0986516475677s
Accuracy | Check White space in annotation for Nomisma.org  took 2.765608787536621s
Consistency | Disjoint class check for Nomisma.org  took 0.49854254722595215s
Consistency | Check Misplaced properties for Nomisma.org  took 29.69489860534668s
Consistency | Check Ontology hijacking for Nomisma.org  took 647.6011943817139s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 29.152506113052368s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.00012683868408203125s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.5037164688110352s
Security | Sign check for Nomisma.org  took 0.4331192970275879s
Availability | Check URIs Dereferenciability for Nomisma.org  took 2159.14319562912s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.156923532485962s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.02127385139465332s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 2.384185791015625e-06s
Believability | Calculation of trust value for Nomisma.org  took 7.62939453125e-06s
INFO | --- Analysis for nomisma_org took 10359.070323467255s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.9405374526977539s
Availability | VoID file availability check for Curriculum Vitae took 0.00026726722717285156s
Extra | Recovery of all triples for Curriculum Vitae took 1.0013465881347656s
Performance | Total latancy measurement for Curriculum Vitae took 1.0816724300384521s
Amount of data | Number of triples check for Curriculum Vitae took 0.28748178482055664s
Interoperability | New terms check for Curriculum Vitae took 1.5918855667114258s
Versatility | Languages check for Curriculum Vitae took 0.13669705390930176s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.28809165954589844s
Interpretability | RDF structures check for Curriculum Vitae took 0.25530076026916504s
Versatility | Serialization formats check for Curriculum Vitae took 0.28079986572265625s
Availability | RDF dump link check for Curriculum Vitae took 0.24435758590698242s
License | MR license check for Curriculum Vitae took 0.2553825378417969s
License | HR license check for Curriculum Vitae took 0.27373814582824707s
Amount of data | Number of property check for Curriculum Vitae took 0.32036590576171875s
Understandability | Number of label check for Curriculum Vitae took 0.2315235137939453s
Understandability | URI regex check for Curriculum Vitae took 0.40254855155944824s
Understandability | Vocabs check for Curriculum Vitae took 0.10941791534423828s
Verifiability | Authors check for Curriculum Vitae took 0.10546135902404785s
Verifiability | Publishers check for Curriculum Vitae took 0.11471247673034668s
Performance | Throughput check for Curriculum Vitae took 10.968730688095093s
Amount of data | Check the number of entities for Curriculum Vitae took 6.794929504394531e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.13101720809936523s
Interlinking | sameAs chians check for Curriculum Vitae took 0.13052129745483398s
Interlinking | skos check for Curriculum Vitae took 0.2975630760192871s
Interlinking | skos check for Curriculum Vitae took 0.24900317192077637s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.2515068054199219s
Currency | Creation date check for Curriculum Vitae took 0.3630967140197754s
Currency | Modification date check for Curriculum Vitae took 0.381117582321167s
Rep.Conc. | URIs length for Curriculum Vitae took 0.5746424198150635s
Interoperability | New vocabularies check for Curriculum Vitae took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.2399129867553711s
Accuracy | Check Functional Property for Curriculum Vitae took 0.11446976661682129s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.14500784873962402s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.2490079402923584s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.0001010894775390625s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0032427310943603516s
Consistency | Disjoint class check for Curriculum Vitae took 0.12199974060058594s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.35280442237854004s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.5371062755584717s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.2978675365447998s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.5540087223052979s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0013477802276611328s
Security | Sign check for Curriculum Vitae took 0.25743770599365234s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 21.2234890460968s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.7058591842651367s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 2.8133392333984375e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.430511474609375e-06s
Believability | Calculation of trust value for Curriculum Vitae took 7.152557373046875e-06s
INFO | --- Analysis for Nordine_Bittich took 64.06111741065979s
Availability | SPARQL endpoint availability check for NorPark took 0.7167575359344482s
Availability | VoID file availability check for NorPark took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for NorPark took 0.7156996726989746s
Reputation | Calculation of the PageRank for NorPark took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for NorPark took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NorPark took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.220008850097656e-05s
Believability | Calculation of trust value for NorPark took 7.867813110351562e-06s
INFO | --- Analysis for norpark took 4.918638229370117s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.02196645736694336s
Availability | VoID file availability check for Parking Dataset took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.24450922012329102s
Reputation | Calculation of the PageRank for Parking Dataset took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.3392181396484375e-05s
Believability | Calculation of trust value for Parking Dataset took 7.62939453125e-06s
INFO | --- Analysis for norpark2 took 2.871814250946045s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.618415117263794s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0002651214599609375s
Extra | Recovery of all triples for Norway fishery stocks dataset took 107.507328748703s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.994887113571167s
Amount of data | Number of triples check for Norway fishery stocks dataset took 8.471582889556885s
Interoperability | New terms check for Norway fishery stocks dataset took 13.716793060302734s
Versatility | Languages check for Norway fishery stocks dataset took 300.2319641113281s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.988208293914795s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.26819491386413574s
Versatility | Serialization formats check for Norway fishery stocks dataset took 9.519655227661133s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.2850649356842041s
License | MR license check for Norway fishery stocks dataset took 0.561790943145752s
License | HR license check for Norway fishery stocks dataset took 300.2121913433075s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.30548787117004395s
Understandability | Number of label check for Norway fishery stocks dataset took 2.5075230598449707s
Understandability | URI regex check for Norway fishery stocks dataset took 0.7634403705596924s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.45517826080322266s
Verifiability | Authors check for Norway fishery stocks dataset took 0.18500924110412598s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.2568931579589844s
Performance | Throughput check for Norway fishery stocks dataset took 11.10519528388977s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 7.319450378417969e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.18396711349487305s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.21404433250427246s
Interlinking | skos check for Norway fishery stocks dataset took 0.45633792877197266s
Interlinking | skos check for Norway fishery stocks dataset took 0.4239954948425293s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 6.091940641403198s
Currency | Creation date check for Norway fishery stocks dataset took 0.4711902141571045s
Currency | Modification date check for Norway fishery stocks dataset took 0.22277474403381348s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 160.4534559249878s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.20544147491455078s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.29274940490722656s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.29671669006347656s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 42.171969413757324s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.6611580848693848s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.6836018562316895s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.2099287509918213s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 84.38261651992798s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.530438899993896s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 37.71411681175232s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.4020464420318604s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 81.25891184806824s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.740903615951538s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5306835174560547s
Security | Sign check for Norway fishery stocks dataset took 0.8502776622772217s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 10.014098405838013s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 1.2740964889526367s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.02115154266357422s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 7.152557373046875e-06s
INFO | --- Analysis for Norway_Fishery_ took 2255.9019722938538s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.39366984367370605s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.685683012008667s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020589590072631836s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.1021575927734375e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 7.3909759521484375e-06s
INFO | --- Analysis for norwegian-geo-divisions took 8.922874450683594s
Availability | SPARQL endpoint availability check for NorwegianSoE took 5.1975250244140625e-05s
Availability | VoID file availability check for NorwegianSoE took 0.00032401084899902344s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.2739241123199463s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.020940303802490234s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 3.147125244140625e-05s
Believability | Calculation of trust value for NorwegianSoE took 9.059906005859375e-06s
INFO | --- Analysis for norwegiansoe took 3.8069934844970703s
Availability | SPARQL endpoint availability check for NITP took 4.649162292480469e-05s
Availability | VoID file availability check for NITP took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for NITP took 0.2566533088684082s
Reputation | Calculation of the PageRank for NITP took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for NITP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for NITP took 7.05718994140625e-05s
Believability | Calculation of trust value for NITP took 7.152557373046875e-06s
INFO | --- Analysis for notIdentifier took 3.4828836917877197s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.267692565917969e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.6970019340515137s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 8.654594421386719e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 6.9141387939453125e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 3.5824568271636963s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.076957702636719e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2637326717376709s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.02082657814025879s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 3.0994415283203125e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 1.1682510375976562e-05s
INFO | --- Analysis for npg took 2.9419853687286377s
Availability | SPARQL endpoint availability check for NPM took 4.553794860839844e-05s
Availability | VoID file availability check for NPM took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for NPM took 0.2613215446472168s
Reputation | Calculation of the PageRank for NPM took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for NPM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for NPM took 3.790855407714844e-05s
Believability | Calculation of trust value for NPM took 6.9141387939453125e-06s
INFO | --- Analysis for npm took 3.2955679893493652s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.04762983322143555s
Availability | VoID file availability check for NTNU special collections took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.2586045265197754s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 6.556510925292969e-05s
Believability | Calculation of trust value for NTNU special collections took 6.9141387939453125e-06s
INFO | --- Analysis for ntnusc took 5.1766581535339355s
Availability | SPARQL endpoint availability check for links took 4.363059997558594e-05s
Availability | VoID file availability check for links took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for links took 0.25573158264160156s
Reputation | Calculation of the PageRank for links took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for links took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for links took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for links took 1.3113021850585938e-05s
Believability | Calculation of trust value for links took 6.9141387939453125e-06s
INFO | --- Analysis for nugmyanmar took 2.277162551879883s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 5.817413330078125e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.28202295303344727s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.775161743164062e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 5.245208740234375e-06s
INFO | --- Analysis for nuts-geovocab took 2.4191300868988037s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.4245645999908447s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0003120899200439453s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.29084181785583496s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.05718994140625e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 7.152557373046875e-06s
INFO | --- Analysis for nvd took 4.024852275848389s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.7931127548217773s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.28079748153686523s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020780563354492188s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.320808410644531e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 7.3909759521484375e-06s
INFO | --- Analysis for nvs took 8.088080167770386s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.2438507080078125e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.2565298080444336s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018978118896484375s
Believability | Calculation of trust value for New York Times - Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.4293100833892822s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.220008850097656e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.23826193809509277s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 2.956390380859375e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 7.152557373046875e-06s
INFO | --- Analysis for o-anc took 2.902857780456543s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.124641418457031e-05s
Availability | VoID file availability check for OANetzwerk took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.2681701183319092s
Reputation | Calculation of the PageRank for OANetzwerk took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.075599670410156e-05s
Believability | Calculation of trust value for OANetzwerk took 7.152557373046875e-06s
INFO | --- Analysis for oanetzwerk took 2.8465850353240967s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.172325134277344e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.24096226692199707s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.0517578125e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 6.9141387939453125e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.8710694313049316s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.42063307762145996s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006916522979736328s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.8335237503051758s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 2.172973155975342s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 3.9273085594177246s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.9424612522125244s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.326170206069946s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.876995325088501s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.40807271003723145s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.36552953720092773s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.7198352813720703s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.4538090229034424s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.5623819828033447s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.32904934883118s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.31690144538879395s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 1.6317415237426758s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.6845729351043701s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.46952295303344727s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.3591160774230957s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.3649132251739502s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 12.351156949996948s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 3.337860107421875e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.3285529613494873s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.38892316818237305s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.34994006156921387s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.20375847816467285s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.40239787101745605s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6993889808654785s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.3104376792907715s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 18.191903114318848s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 1.3128314018249512s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.2802152633666992s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.8373994827270508s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 1.0920777320861816s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.0241396427154541s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.02790975570678711s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.30607080459594727s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 13.473461627960205s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.3748011589050293s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.1814663410186768s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.2504961490631104s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 17.50599980354309s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03166365623474121s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.38066887855529785s
Security | Sign check for Italian Chamber of Deputies - official dataset took 1.6534297466278076s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 11.200812339782715s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3559534549713135s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00012731552124023438s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 6.67572021484375e-06s
INFO | --- Analysis for ocd took 441.9504508972168s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.57763671875e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2611532211303711s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.02090144157409668s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.3392181396484375e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.1444091796875e-05s
INFO | --- Analysis for oceandrilling-borehole took 4.321514368057251s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.359588623046875s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2526512145996094s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 9.274482727050781e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-codices took 7.104020357131958s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.2009265422821045s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.25223755836486816s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.5762786865234375e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 5.697849988937378s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.1665666103363037s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2747814655303955s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.4809112548828125e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.1682510375976562e-05s
INFO | --- Analysis for oceandrilling-forams took 5.896383047103882s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.1189689636230469s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.27895665168762207s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020772695541381836s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.314018249511719e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-janus took 6.032647132873535s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 11.005232572555542s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.262678861618042s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.409385681152344e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-janusamp took 15.75411605834961s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.398505449295044s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0008170604705810547s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2680506706237793s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0009450912475585938s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.266334533691406e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.147125244140625e-05s
INFO | --- Analysis for oceandrilling-ldeo took 6.068758726119995s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.3392181396484375e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2689337730407715s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.888938903808594e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 7.867813110351562e-06s
INFO | --- Analysis for oclc-fast took 9.85993480682373s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.315376281738281e-05s
Availability | VoID file availability check for Open Data Communities took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.2894890308380127s
Reputation | Calculation of the PageRank for Open Data Communities took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 4.601478576660156e-05s
Believability | Calculation of trust value for Open Data Communities took 8.821487426757812e-06s
INFO | --- Analysis for odc took 2.976698637008667s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.57763671875e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.5363459587097168s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.28717947006225586s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.0994415283203125e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.245208740234375e-06s
INFO | --- Analysis for odc-imd-environment-score took 4.877679347991943s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 6.628036499023438e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2653992176055908s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.8848648071289062e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 7.152557373046875e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 2.9692134857177734s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.7774829864501953s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.7642133235931396s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2575507164001465s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.528594970703125e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.4836273193359375e-06s
INFO | --- Analysis for odc-lsoa took 6.442619562149048s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.172325134277344e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2671499252319336s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.8133392333984375e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 7.867813110351562e-06s
INFO | --- Analysis for odc-population-2005 took 2.9194178581237793s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 5.1975250244140625e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.2635173797607422s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 7.62939453125e-06s
INFO | --- Analysis for ods took 2.8648200035095215s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.4335670471191406s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0011181831359863281s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2651329040527344s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020452499389648438s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.655952453613281e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for oecd-linked-data took 2.8604955673217773s
Availability | SPARQL endpoint availability check for Offener Haushalt took 5.602836608886719e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.26828622817993164s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 2.8133392333984375e-05s
Believability | Calculation of trust value for Offener Haushalt took 7.152557373046875e-06s
INFO | --- Analysis for offener-haushalt took 2.9361233711242676s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.2112774848938s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2808992862701416s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.02114415168762207s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0008661746978759766s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.9591064453125e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 8.106231689453125e-06s
INFO | --- Analysis for ogolod took 102.73132371902466s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.363059997558594e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.2734646797180176s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0009677410125732422s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.267692565917969e-05s
Believability | Calculation of trust value for OLAC Metadata took 7.152557373046875e-06s
INFO | --- Analysis for olac took 22.650435209274292s
Availability | SPARQL endpoint availability check for OLiA took 4.3392181396484375e-05s
Availability | VoID file availability check for OLiA took 0.0007760524749755859s
Completeness | Calculation of interlinking completeness for OLiA took 0.2759363651275635s
Reputation | Calculation of the PageRank for OLiA took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for OLiA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0008120536804199219s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012373924255371094s
Believability | Calculation of trust value for OLiA took 6.9141387939453125e-06s
INFO | --- Analysis for olia took 12.418378114700317s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.410743713378906e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.26657629013061523s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.9577484130859375e-05s
Believability | Calculation of trust value for OLiA Discourse took 7.867813110351562e-06s
INFO | --- Analysis for olia-discourse took 8.194952011108398s
Availability | SPARQL endpoint availability check for Open Land Use took 0.2997269630432129s
Availability | VoID file availability check for Open Land Use took 0.0002732276916503906s
Extra | Recovery of all triples for Open Land Use took 116.63300728797913s
Performance | Total latancy measurement for Open Land Use took 0.9507637023925781s
Amount of data | Number of triples check for Open Land Use took 7.930659770965576s
Interoperability | New terms check for Open Land Use took 15.576716423034668s
Versatility | Languages check for Open Land Use took 300.2136836051941s
Interpretability | Number of blank nodes check for Open Land Use took 3.2407050132751465s
Interpretability | RDF structures check for Open Land Use took 0.27686452865600586s
Versatility | Serialization formats check for Open Land Use took 12.354958772659302s
Availability | RDF dump link check for Open Land Use took 0.2637948989868164s
License | MR license check for Open Land Use took 0.5941758155822754s
License | HR license check for Open Land Use took 300.2200059890747s
Amount of data | Number of property check for Open Land Use took 0.2807016372680664s
Understandability | Number of label check for Open Land Use took 2.9090781211853027s
Understandability | URI regex check for Open Land Use took 0.8000316619873047s
Understandability | Vocabs check for Open Land Use took 0.49165797233581543s
Verifiability | Authors check for Open Land Use took 0.21675968170166016s
Verifiability | Publishers check for Open Land Use took 0.24352073669433594s
Performance | Throughput check for Open Land Use took 11.617553472518921s
Amount of data | Check the number of entities for Open Land Use took 8.177757263183594e-05s
Verifiability | Contribs. check for Open Land Use took 0.2111647129058838s
Interlinking | sameAs chians check for Open Land Use took 0.20093584060668945s
Interlinking | skos check for Open Land Use took 0.4672691822052002s
Interlinking | skos check for Open Land Use took 0.43256092071533203s
Timeliness | dataset update frequency check for Open Land Use took 7.307652950286865s
Currency | Creation date check for Open Land Use took 0.46764159202575684s
Currency | Modification date check for Open Land Use took 0.23131155967712402s
Rep.Conc. | URIs length for Open Land Use took 161.57714223861694s
Interoperability | New vocabularies check for Open Land Use took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.19465923309326172s
Accuracy | Check Functional Property for Open Land Use took 0.24832534790039062s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.2450242042541504s
Accuracy | Check Empty annotation labels for Open Land Use took 36.82084631919861s
Accuracy | Check White space in annotation for Open Land Use took 2.679685592651367s
Accuracy | Check Datatype consistency for Open Land Use took 2.670774221420288s
Consistency | Disjoint class check for Open Land Use took 0.20874881744384766s
Consistency | Check Misplaced properties for Open Land Use took 82.90063405036926s
Consistency | Misplaced classes for Open Land Use took 8.595360279083252s
Consistency | Check Ontology hijacking for Open Land Use took 35.02488398551941s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.3671329021453857s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 86.16982531547546s
Conciseness | Check Extensional conciseness for Open Land Use took 2.7519307136535645s
Conciseness | Check Intensional conciseness for Open Land Use took 0.5223515033721924s
Security | Sign check for Open Land Use took 0.7448713779449463s
Availability | Check URIs Dereferenciability for Open Land Use took 9.493010997772217s
Completeness | Calculation of interlinking completeness for Open Land Use took 1.184103012084961s
Reputation | Calculation of the PageRank for Open Land Use took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 5.4836273193359375e-06s
Believability | Calculation of trust value for Open Land Use took 8.58306884765625e-06s
INFO | --- Analysis for OLU took 2263.1637530326843s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.172325134277344e-05s
Availability | VoID file availability check for OmegaWiki took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.25527143478393555s
Reputation | Calculation of the PageRank for OmegaWiki took 0.02031421661376953s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 2.86102294921875e-05s
Believability | Calculation of trust value for OmegaWiki took 7.152557373046875e-06s
INFO | --- Analysis for omegawiki took 4.292026519775391s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.8422892093658447s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.25818657875061035s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-als took 5.4382641315460205s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.24456477165222168s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.28162550926208496s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.457069396972656e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-arb took 3.070530891418457s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.20354127883911133s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2770881652832031s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-bul took 2.976174831390381s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.20955348014831543s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0003662109375s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2574043273925781s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-cow took 2.8577706813812256s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.20590472221374512s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.26509666442871094s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
INFO | --- Analysis for omwn-cwn took 3.308359146118164s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.20893073081970215s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.282515287399292s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020345687866210938s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-dan took 2.890890121459961s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.21097111701965332s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.00035762786865234375s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.25079798698425293s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-ell took 2.981501817703247s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.20201992988586426s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.25819849967956543s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-eng took 2.886805534362793s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.22221922874450684s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.24240779876708984s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.02025747299194336s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.3855438232421875e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-fas took 2.8450992107391357s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2187802791595459s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2676887512207031s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-fin took 2.914303779602051s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.20686650276184082s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2633330821990967s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0009620189666748047s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-fra took 2.9186503887176514s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2137453556060791s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.26848793029785156s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-heb took 2.869251012802124s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.20036888122558594s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2657184600830078s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020479679107666016s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-hrv took 2.892801284790039s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.22426342964172363s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.24796485900878906s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-isl took 2.9297637939453125s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.19921350479125977s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2686152458190918s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-ita took 2.913456916809082s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.20741486549377441s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.267087459564209s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-iwn took 2.8704726696014404s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.20595002174377441s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.27399253845214844s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.02103400230407715s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-jpn took 2.9434926509857178s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.19464945793151855s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.26668286323547363s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.02042412757873535s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-mcr took 2.8742759227752686s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.19901490211486816s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2610201835632324s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-msa took 2.834834575653076s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.20629358291625977s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.25673913955688477s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-nld took 2.8903114795684814s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.1907045841217041s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.26227235794067383s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-nor took 2.9253392219543457s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.21978211402893066s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2755439281463623s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020413875579833984s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-pol took 2.903095245361328s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.19591665267944336s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.27779650688171387s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.020177125930786133s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-por took 2.808328628540039s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.17515254020690918s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.00033211708068847656s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.28491759300231934s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
INFO | --- Analysis for omwn-ron took 2.959376811981201s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.22011685371398926s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.26680588722229004s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-slk took 2.966736078262329s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.19864940643310547s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2574753761291504s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-slv took 2.9213595390319824s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.17616844177246094s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.26181960105895996s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.811981201171875e-05s
INFO | --- Analysis for omwn-swe took 2.8549082279205322s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.2008054256439209s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2819972038269043s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-tha took 2.931663751602173s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 5.559398889541626s
Availability | VoID file availability check for OntoBeef Domain took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.27285027503967285s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.1484832763671875e-05s
Believability | Calculation of trust value for OntoBeef Domain took 7.152557373046875e-06s
INFO | --- Analysis for ontobeef-domain took 36.02945685386658s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.267692565917969e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.2640664577484131s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.322166442871094e-05s
Believability | Calculation of trust value for Ontos News Portal took 6.9141387939453125e-06s
INFO | --- Analysis for ontos-news-portal took 5.280191898345947s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 5.221366882324219e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.24752068519592285s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0008347034454345703s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.4332275390625e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.867813110351562e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.512343168258667s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.1961669921875e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.2482924461364746s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.910064697265625e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 6.67572021484375e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 10.338744640350342s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.270526647567749s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 3.170967102050781e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 7.867813110351562e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.9438211917877197s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.291534423828125e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.2583193778991699s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 5.364418029785156e-05s
Believability | Calculation of trust value for Open Data Euskadi took 5.0067901611328125e-06s
INFO | --- Analysis for open-data-euskadi took 8.667583227157593s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.1484832763671875e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0003330707550048828s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.2838740348815918s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.0001049041748046875s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.62939453125e-06s
INFO | --- Analysis for open-data-risp took 7.552732467651367s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.2803676128387451s
Availability | VoID file availability check for Open Data Thesaurus took 0.0007450580596923828s
Extra | Recovery of all triples for Open Data Thesaurus took 1.5389444828033447s
Performance | Total latancy measurement for Open Data Thesaurus took 0.5259878635406494s
Amount of data | Number of triples check for Open Data Thesaurus took 0.12465572357177734s
Interoperability | New terms check for Open Data Thesaurus took 1.393144130706787s
Versatility | Languages check for Open Data Thesaurus took 0.1324021816253662s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.14435911178588867s
Security | Check HTTPS for Open Data Thesaurus took 0.364152193069458s
Interpretability | RDF structures check for Open Data Thesaurus took 0.17645263671875s
Versatility | Serialization formats check for Open Data Thesaurus took 0.1250779628753662s
Availability | RDF dump link check for Open Data Thesaurus took 1.1292850971221924s
License | MR license check for Open Data Thesaurus took 0.13925695419311523s
License | HR license check for Open Data Thesaurus took 0.12271451950073242s
Amount of data | Number of property check for Open Data Thesaurus took 0.13765811920166016s
Understandability | Number of label check for Open Data Thesaurus took 0.11568522453308105s
Understandability | URI regex check for Open Data Thesaurus took 0.18515801429748535s
Understandability | Vocabs check for Open Data Thesaurus took 0.1511363983154297s
Verifiability | Authors check for Open Data Thesaurus took 0.13295221328735352s
Verifiability | Publishers check for Open Data Thesaurus took 0.13922500610351562s
Performance | Throughput check for Open Data Thesaurus took 10.461989879608154s
Amount of data | Check the number of entities for Open Data Thesaurus took 0.0001685619354248047s
Verifiability | Contribs. check for Open Data Thesaurus took 0.11523890495300293s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.11487174034118652s
Interlinking | skos check for Open Data Thesaurus took 0.1327991485595703s
Interlinking | skos check for Open Data Thesaurus took 0.10337615013122559s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.09415602684020996s
Currency | Creation date check for Open Data Thesaurus took 0.19652128219604492s
Currency | Modification date check for Open Data Thesaurus took 0.2246379852294922s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4781074523925781s
Interoperability | New vocabularies check for Open Data Thesaurus took 1.1704347133636475s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.1291215419769287s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.11297011375427246s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.10687398910522461s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1928730010986328s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011081695556640625s
Consistency | Disjoint class check for Open Data Thesaurus took 0.07844042778015137s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.1873784065246582s
Consistency | Misplaced classes for Open Data Thesaurus took 0.07913351058959961s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.4718573093414307s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.401200771331787s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0001652240753173828s
Security | Sign check for Open Data Thesaurus took 0.09981036186218262s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.24780893325805664s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.019925594329833984s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.47776150703430176s
Believability | Calculation of trust value for Open Data Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for open-data-thesaurus took 91.58410382270813s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.1961669921875e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2585275173187256s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 3.24249267578125e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 8.106231689453125e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.928751230239868s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.9114227294921875e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.27060770988464355s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.747245788574219e-05s
Believability | Calculation of trust value for Open Election Data Project took 5.9604644775390625e-06s
INFO | --- Analysis for open-election-data-project took 2.4176673889160156s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.8312439918518066s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.26383042335510254s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.021068572998046875s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 9.012222290039062e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 5.7220458984375e-06s
INFO | --- Analysis for open-energy-info-wiki took 10.56421446800232s
Availability | SPARQL endpoint availability check for Open Library took 4.458427429199219e-05s
Availability | VoID file availability check for Open Library took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for Open Library took 0.28372812271118164s
Reputation | Calculation of the PageRank for Open Library took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Open Library took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.104873657226562e-05s
Believability | Calculation of trust value for Open Library took 7.3909759521484375e-06s
INFO | --- Analysis for open-library took 10.250176429748535s
Availability | SPARQL endpoint availability check for Open Directory took 4.0531158447265625e-05s
Availability | VoID file availability check for Open Directory took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Open Directory took 0.26091456413269043s
Reputation | Calculation of the PageRank for Open Directory took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.123283386230469e-05s
Believability | Calculation of trust value for Open Directory took 7.3909759521484375e-06s
INFO | --- Analysis for open_directory took 2.9746625423431396s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.18785500526428223s
Availability | VoID file availability check for Open Land Use @PSNC took 0.00027251243591308594s
Extra | Recovery of all triples for Open Land Use @PSNC took 118.42070055007935s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9834375381469727s
Amount of data | Number of triples check for Open Land Use @PSNC took 8.745498657226562s
Interoperability | New terms check for Open Land Use @PSNC took 13.921780824661255s
Versatility | Languages check for Open Land Use @PSNC took 300.16310572624207s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.86365008354187s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.2667219638824463s
Versatility | Serialization formats check for Open Land Use @PSNC took 9.7523033618927s
Availability | RDF dump link check for Open Land Use @PSNC took 0.2902061939239502s
License | MR license check for Open Land Use @PSNC took 0.5867037773132324s
License | HR license check for Open Land Use @PSNC took 300.1811213493347s
Amount of data | Number of property check for Open Land Use @PSNC took 0.21690940856933594s
Understandability | Number of label check for Open Land Use @PSNC took 2.4836905002593994s
Understandability | URI regex check for Open Land Use @PSNC took 0.6381735801696777s
Understandability | Vocabs check for Open Land Use @PSNC took 0.3314814567565918s
Verifiability | Authors check for Open Land Use @PSNC took 0.19964003562927246s
Verifiability | Publishers check for Open Land Use @PSNC took 0.27149152755737305s
Performance | Throughput check for Open Land Use @PSNC took 11.3290696144104s
Amount of data | Check the number of entities for Open Land Use @PSNC took 6.890296936035156e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.21064352989196777s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.20940446853637695s
Interlinking | skos check for Open Land Use @PSNC took 0.45589447021484375s
Interlinking | skos check for Open Land Use @PSNC took 0.45964741706848145s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 5.946844100952148s
Currency | Creation date check for Open Land Use @PSNC took 0.49078798294067383s
Currency | Modification date check for Open Land Use @PSNC took 0.2139277458190918s
Rep.Conc. | URIs length for Open Land Use @PSNC took 146.00725269317627s
Interoperability | New vocabularies check for Open Land Use @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.21101665496826172s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.3240952491760254s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.3358330726623535s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 37.906675577163696s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.6700994968414307s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.679384469985962s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.19486498832702637s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 82.64716625213623s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.448568344116211s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 36.11193895339966s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.3413424491882324s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 84.55848121643066s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.7475669384002686s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.520806074142456s
Security | Sign check for Open Land Use @PSNC took 0.9438309669494629s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 10.323181629180908s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.5509133338928223s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 6.67572021484375e-06s
INFO | --- Analysis for Open_Land_Use took 2217.070404291153s
Availability | SPARQL endpoint availability check for flyatlas took 1.7163677215576172s
Availability | VoID file availability check for flyatlas took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for flyatlas took 0.27313685417175293s
Reputation | Calculation of the PageRank for flyatlas took 0.021377086639404297s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for flyatlas took 2.956390380859375e-05s
Believability | Calculation of trust value for flyatlas took 7.3909759521484375e-06s
INFO | --- Analysis for openbiomed-flyatlas took 10.928792476654053s
Availability | SPARQL endpoint availability check for OpenCalais took 4.267692565917969e-05s
Availability | VoID file availability check for OpenCalais took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.27480220794677734s
Reputation | Calculation of the PageRank for OpenCalais took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00011086463928222656s
Believability | Calculation of trust value for OpenCalais took 6.67572021484375e-06s
INFO | --- Analysis for opencalais took 7.4023659229278564s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 6.413459777832031e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.24091506004333496s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.462501525878906e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 5.0067901611328125e-06s
INFO | --- Analysis for opencorporates took 4.121413707733154s
Availability | SPARQL endpoint availability check for OpenCyc took 4.291534423828125e-05s
Availability | VoID file availability check for OpenCyc took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.24891424179077148s
Reputation | Calculation of the PageRank for OpenCyc took 0.020837068557739258s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0008122920989990234s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00013947486877441406s
Believability | Calculation of trust value for OpenCyc took 6.9141387939453125e-06s
INFO | --- Analysis for opencyc took 3.3149640560150146s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.9114227294921875e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.28443193435668945s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.337860107421875e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.3471837043762207s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.2837519645690918s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.0209352970123291s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0009472370147705078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.3158013820648193s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.00040435791015625s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.25048112869262695s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.71661376953125e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.9060754776000977s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 8.440017700195312e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2499837875366211s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 3.2219502925872803s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.00041294097900390625s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.24835586547851562s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.035176992416382s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.24757933616638184s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.8080005645751953s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0003566741943359375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.25615692138671875s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02035355567932129s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.7598798274993896s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0003712177276611328s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.24880385398864746s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.32484769821167s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.26807451248168945s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.146547555923462s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.28969550132751465s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 3.17350697517395s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.26117825508117676s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020392894744873047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.933100461959839s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.24556565284729004s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.865290641784668s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.26398611068725586s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.505023241043091s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 5.3882598876953125e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.26471543312072754s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020212650299072266s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.4037230014801025s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.27660441398620605s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020123004913330078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.885457754135132s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.744529724121094e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2677881717681885s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 5.984306335449219e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.994154453277588s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.29881882667541504s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.021413564682006836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.04921555519104s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.25432872772216797s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.020220518112182617s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.8932456970214844s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2434542179107666s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.3664615154266357s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007910728454589844s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2839348316192627s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0009479522705078125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.935264587402344e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.955939531326294s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0007987022399902344s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.26728153228759766s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.0204312801361084s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.892279863357544s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.28765034675598145s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.02064657211303711s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.000885009765625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.972362518310547s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.24355769157409668s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.9072091579437256s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0008449554443359375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.25651121139526367s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020747661590576172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.9097752571105957s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.1975250244140625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.28826117515563965s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.0806634426116943s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007944107055664062s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2709064483642578s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 3.0904152393341064s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2416999340057373s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.8752217292785645s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.28078794479370117s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02026057243347168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.8809189796447754s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.2724771499633789s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.021808862686157227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.14984130859375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.927614688873291s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.2744412422180176s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.021134614944458008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.8958470821380615s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2867581844329834s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020479202270507812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.949174642562866s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007829666137695312s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2758140563964844s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020824909210205078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.9267590045928955s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.262984037399292s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0008575916290283203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.970553159713745s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.3882598876953125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.2588932514190674s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.335514783859253s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.26242613792419434s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.385852813720703s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 5.340576171875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.27523279190063477s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.018850803375244s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2707672119140625s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.0016865730285645s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.34957146644592285s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0009484291076660156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.7206878662109375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 3.0587170124053955s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.278367280960083s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.8512067794799805s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 6.890296936035156e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2855262756347656s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 6.4849853515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.9820556640625s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.2538151741027832s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02695178985595703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0010793209075927734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.1292388439178467s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.839897155761719e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.28621864318847656s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.826392412185669s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0005924701690673828s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2662050724029541s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.8475289344787598s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.023661851882935s
Availability | VoID file availability check for Open Data of Ecuador took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2589101791381836s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020323514938354492s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.392333984375e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 7.152557373046875e-06s
INFO | --- Analysis for opendataec took 8.800925254821777s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.267692565917969e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2851684093475342s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.523646354675293s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.315376281738281e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2641866207122803s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 6.651878356933594e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.919992685317993s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.220008850097656e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2792088985443115s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.7851600646972656s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.28652143478393555s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.7995030879974365s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.27014732360839844s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.6758062839508057s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 5.125999450683594e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2558913230895996s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 5.745887756347656e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.7601406574249268s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 7.104873657226562e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2528116703033447s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.021045446395874023s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.7802581787109375s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2635617256164551s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.7534849643707275s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0003037452697753906s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.28690528869628906s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020653486251831055s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.239776611328125e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.4439570903778076s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.443763971328735s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.29297542572021484s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.02111053466796875s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.4332275390625e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.3828277587890625e-05s
INFO | --- Analysis for openlink-lod-cache took 62.989335775375366s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 5.316734313964844e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.28401708602905273s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.441375732421875e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.049041748046875e-05s
INFO | --- Analysis for openlinksw-dataspaces took 2.570786237716675s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.673004150390625e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.2588632106781006s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.465217590332031e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 5.245208740234375e-06s
INFO | --- Analysis for openlylocal took 7.7353692054748535s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 0.860680341720581s
Availability | VoID file availability check for OpenMobileNetwork took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2865922451019287s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.653236389160156e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 7.152557373046875e-06s
INFO | --- Analysis for openmobilenetwork took 3.760801076889038s
Availability | SPARQL endpoint availability check for OpenTox took 4.029273986816406e-05s
Availability | VoID file availability check for OpenTox took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for OpenTox took 0.26429152488708496s
Reputation | Calculation of the PageRank for OpenTox took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.170967102050781e-05s
Believability | Calculation of trust value for OpenTox took 7.3909759521484375e-06s
INFO | --- Analysis for opentox took 2.937404155731201s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.267692565917969e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.29291319847106934s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.020975112915039062s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 7.62939453125e-06s
INFO | --- Analysis for openuplabs took 2.961893081665039s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.291534423828125e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.25426506996154785s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020238399505615234s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 2.9087066650390625e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 7.3909759521484375e-06s
INFO | --- Analysis for opus took 2.876715660095215s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 4.1961669921875e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.2649247646331787s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.695487976074219e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 7.62939453125e-06s
INFO | --- Analysis for orcid took 2.948085069656372s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.9975380897521973s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.25020289421081543s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.1552734375e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 5.437257528305054s
Availability | SPARQL endpoint availability check for oreilly took 4.172325134277344e-05s
Availability | VoID file availability check for oreilly took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for oreilly took 0.25439906120300293s
Reputation | Calculation of the PageRank for oreilly took 0.020215749740600586s
Interlinking | Calculation of Degree of Connection for oreilly took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.5299530029296875e-05s
Believability | Calculation of trust value for oreilly took 6.9141387939453125e-06s
INFO | --- Analysis for oreilly took 4.734653472900391s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.4135987758636475s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.29261112213134766s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 7.867813110351562e-06s
INFO | --- Analysis for Organchem-Data took 7.392822980880737s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.07406353950500488s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0011105537414550781s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2687997817993164s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.021085262298583984s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0009388923645019531s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 8.0108642578125e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for organic-edunet took 9.565927743911743s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.48613691329956055s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005848407745361328s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 13.737902641296387s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7677035331726074s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.2061481475830078s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.620868444442749s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 6.537113428115845s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.15610718727111816s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.1455836296081543s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.18721842765808105s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.16491198539733887s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.14744853973388672s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.9204485416412354s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.1815776824951172s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.3366076946258545s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.3370084762573242s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.17822837829589844s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.13882207870483398s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.13519597053527832s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.908714056015015s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 8.702278137207031e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.17077016830444336s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.33050036430358887s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.18253493309020996s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 1.0188915729522705s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.1283113956451416s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.3163187503814697s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.28908419609069824s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 7.6167151927948s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.14315390586853027s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.2200467586517334s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.203277587890625s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 7.843622922897339s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.14740872383117676s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.28005337715148926s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.34178853034973145s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.5221056938171387s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.9184627532958984s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 5.6146533489227295s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.3344731330871582s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.2903928756713867s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2848935127258301s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.18662238121032715s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.16053485870361328s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2102.1198637485504s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 1.1649832725524902s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.02100968360900879s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 7.867813110351562e-06s
INFO | --- Analysis for orkg took 2388.6191461086273s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.053118944168091s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0003509521484375s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.2821311950683594s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.940696716308594e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 7.867813110351562e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 30.39991593360901s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.5877037048339844s
Availability | VoID file availability check for OSM Semantic Network took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.25620460510253906s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.457069396972656e-05s
Believability | Calculation of trust value for OSM Semantic Network took 7.152557373046875e-06s
INFO | --- Analysis for osm-semantic-network took 10.04357099533081s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.5485856533050537s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00029087066650390625s
Extra | Recovery of all triples for Open Transport Map @PSNC took 124.30181407928467s
Performance | Total latancy measurement for Open Transport Map @PSNC took 1.0101172924041748s
Amount of data | Number of triples check for Open Transport Map @PSNC took 8.272260427474976s
Interoperability | New terms check for Open Transport Map @PSNC took 14.081400156021118s
Versatility | Languages check for Open Transport Map @PSNC took 300.26034140586853s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 3.3981683254241943s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.2802112102508545s
Versatility | Serialization formats check for Open Transport Map @PSNC took 10.727590084075928s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.2941093444824219s
License | MR license check for Open Transport Map @PSNC took 0.5350203514099121s
License | HR license check for Open Transport Map @PSNC took 300.23033380508423s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.5626215934753418s
Understandability | Number of label check for Open Transport Map @PSNC took 2.49147891998291s
Understandability | URI regex check for Open Transport Map @PSNC took 0.8547616004943848s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.4493391513824463s
Verifiability | Authors check for Open Transport Map @PSNC took 0.21700620651245117s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.25961899757385254s
Performance | Throughput check for Open Transport Map @PSNC took 11.650375843048096s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 7.271766662597656e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.2003028392791748s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.21043944358825684s
Interlinking | skos check for Open Transport Map @PSNC took 0.461916446685791s
Interlinking | skos check for Open Transport Map @PSNC took 0.4534633159637451s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 5.603599548339844s
Currency | Creation date check for Open Transport Map @PSNC took 0.472567081451416s
Currency | Modification date check for Open Transport Map @PSNC took 0.21131634712219238s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 162.25045132637024s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.20427155494689941s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.3323850631713867s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.3364861011505127s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 37.83973145484924s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.66438627243042s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.6646246910095215s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.19201302528381348s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 80.28260135650635s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.393774032592773s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 34.12182950973511s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.3892862796783447s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 88.59557008743286s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.762845039367676s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.6583080291748047s
Security | Sign check for Open Transport Map @PSNC took 0.7615706920623779s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 9.868860721588135s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 1.3355376720428467s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.021320343017578125s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for OTM took 2278.112746477127s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.25243115425109863s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 2.9802322387695312e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 7.867813110351562e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 4.190855503082275s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.1961669921875e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002982616424560547s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.3001537322998047s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.528594970703125e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.62939453125e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 4.357665300369263s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.291534423828125e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.2654409408569336s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 3.7646374702453613s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 5.269050598144531e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.2802114486694336s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.7894973754882812e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 1.430511474609375e-05s
INFO | --- Analysis for ox-ac-uk-openmeters took 3.4010121822357178s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.267692565917969e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.26950693130493164s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 3.4038212299346924s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.291534423828125e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.26520371437072754s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 2.765655517578125e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 6.198883056640625e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.8727307319641113s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.1484832763671875e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.24744534492492676s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.870447874069214s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.220008850097656e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.28489136695861816s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.956390380859375e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for oxpoints took 2.876291513442993s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 23.1079740524292s
Availability | VoID file availability check for Pali English Lexicon took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.27504587173461914s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.021088600158691406s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.337860107421875e-05s
Believability | Calculation of trust value for Pali English Lexicon took 7.867813110351562e-06s
INFO | --- Analysis for pali-english-lexicon took 52.18645477294922s
Availability | SPARQL endpoint availability check for PanLex took 0.3709895610809326s
Availability | VoID file availability check for PanLex took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for PanLex took 0.266664981842041s
Reputation | Calculation of the PageRank for PanLex took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.343292236328125e-05s
Believability | Calculation of trust value for PanLex took 8.344650268554688e-06s
INFO | --- Analysis for panlex took 2.8595101833343506s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 6.008148193359375e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.27410316467285156s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.814697265625e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 8.106231689453125e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 6.531783819198608s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.21744751930236816s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.26572155952453613s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.078315734863281e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.705925703048706s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 5.340576171875e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.27666735649108887s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.719329833984375e-05s
Believability | Calculation of trust value for PDEV-Lemon took 7.867813110351562e-06s
INFO | --- Analysis for pdev-lemon took 4.000180959701538s
Availability | SPARQL endpoint availability check for pdevlemon took 4.5299530029296875e-05s
Availability | VoID file availability check for pdevlemon took 0.0012068748474121094s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.266162633895874s
Reputation | Calculation of the PageRank for pdevlemon took 0.02083730697631836s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.001071929931640625s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.695487976074219e-05s
Believability | Calculation of trust value for pdevlemon took 9.298324584960938e-06s
INFO | --- Analysis for pdevlemon took 3.231621742248535s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 5.53131103515625e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008871555328369141s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.27103471755981445s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.058547973632812e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 6.9141387939453125e-06s
INFO | --- Analysis for periodo took 18.77906608581543s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.5299530029296875e-05s
Availability | VoID file availability check for Personal_Homepages took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.2599020004272461s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020696401596069336s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.000385284423828125s
Believability | Calculation of trust value for Personal_Homepages took 8.344650268554688e-06s
INFO | --- Analysis for personal-homepages took 2.3887879848480225s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology of University People took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.28818297386169434s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020786762237548828s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.0517578125e-05s
Believability | Calculation of trust value for Ontology of University People took 7.867813110351562e-06s
INFO | --- Analysis for PersonOnto took 2.4456024169921875s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 8.090413570404053s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.28418469429016113s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1205673217773438e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.3909759521484375e-06s
INFO | --- Analysis for PFKHS took 14.315801858901978s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.826836824417114s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.25876855850219727s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2636184692382812e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.867813110351562e-06s
INFO | --- Analysis for PFRPPH took 11.13338041305542s
Availability | SPARQL endpoint availability check for PGxLOD took 0.4132561683654785s
Availability | VoID file availability check for PGxLOD took 0.0005669593811035156s
Extra | Recovery of all triples for PGxLOD took 2.1836860179901123s
Performance | Total latancy measurement for PGxLOD took 0.8057091236114502s
Amount of data | Number of triples check for PGxLOD took 0.8203766345977783s
Interoperability | New terms check for PGxLOD took 1.9995601177215576s
Versatility | Languages check for PGxLOD took 60.22681736946106s
Interpretability | Number of blank nodes check for PGxLOD took 1.453263759613037s
Interpretability | RDF structures check for PGxLOD took 0.44074392318725586s
Versatility | Serialization formats check for PGxLOD took 0.17807650566101074s
Availability | RDF dump link check for PGxLOD took 53.105146169662476s
License | MR license check for PGxLOD took 0.1817924976348877s
License | HR license check for PGxLOD took 60.86158013343811s
Amount of data | Number of property check for PGxLOD took 0.1624002456665039s
Understandability | Number of label check for PGxLOD took 0.7864270210266113s
Understandability | URI regex check for PGxLOD took 0.33347225189208984s
Understandability | Vocabs check for PGxLOD took 0.15424442291259766s
Verifiability | Authors check for PGxLOD took 0.18669342994689941s
Verifiability | Publishers check for PGxLOD took 0.16808557510375977s
Performance | Throughput check for PGxLOD took 10.906291007995605s
Amount of data | Check the number of entities for PGxLOD took 0.11880302429199219s
Verifiability | Contribs. check for PGxLOD took 0.17297983169555664s
Interlinking | sameAs chians check for PGxLOD took 0.2987649440765381s
Interlinking | skos check for PGxLOD took 0.22991704940795898s
Interlinking | skos check for PGxLOD took 0.21485257148742676s
Timeliness | dataset update frequency check for PGxLOD took 0.17526865005493164s
Currency | Creation date check for PGxLOD took 0.37702322006225586s
Currency | Modification date check for PGxLOD took 0.38985228538513184s
Rep.Conc. | URIs length for PGxLOD took 6.81194281578064s
Interoperability | New vocabularies check for PGxLOD took 43.15571069717407s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.1674654483795166s
Accuracy | Check Functional Property for PGxLOD took 0.1972520351409912s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.18623018264770508s
Accuracy | Check Empty annotation labels for PGxLOD took 1.0839824676513672s
Accuracy | Check White space in annotation for PGxLOD took 0.037067413330078125s
Accuracy | Check Datatype consistency for PGxLOD took 0.028028011322021484s
Consistency | Disjoint class check for PGxLOD took 0.1785144805908203s
Consistency | Check Misplaced properties for PGxLOD took 6.612994432449341s
Consistency | Misplaced classes for PGxLOD took 0.3049437999725342s
Consistency | Check Ontology hijacking for PGxLOD took 2.072282552719116s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.2534286975860596s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.143661737442017s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03724098205566406s
Conciseness | Check Intensional conciseness for PGxLOD took 0.26206350326538086s
Security | Sign check for PGxLOD took 0.18242359161376953s
Availability | Check URIs Dereferenciability for PGxLOD took 1627.083058834076s
Completeness | Calculation of interlinking completeness for PGxLOD took 1.6876769065856934s
Reputation | Calculation of the PageRank for PGxLOD took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 18.33080792427063s
Believability | Calculation of trust value for PGxLOD took 7.3909759521484375e-06s
INFO | --- Analysis for PGxLOD took 3011.3263971805573s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1701419353485107s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.2711200714111328s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 4.00543212890625e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 8.821487426757812e-06s
INFO | --- Analysis for phoible took 6.760790109634399s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.1961669921875e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.2950325012207031s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 2.9802322387695312e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 7.3909759521484375e-06s
INFO | --- Analysis for PISM took 12.686666011810303s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.3392181396484375e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2633535861968994s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.0208127498626709s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.749961853027344e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 8.106231689453125e-06s
INFO | --- Analysis for planetdata-project-wiki took 3.7772574424743652s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.2366936206817627s
Availability | VoID file availability check for digitized plant specimen took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.25754809379577637s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.890296936035156e-05s
Believability | Calculation of trust value for digitized plant specimen took 7.152557373046875e-06s
INFO | --- Analysis for plant-specimen took 4.515818119049072s
Availability | SPARQL endpoint availability check for Pleiades took 7.05718994140625e-05s
Availability | VoID file availability check for Pleiades took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Pleiades took 0.29152464866638184s
Reputation | Calculation of the PageRank for Pleiades took 0.020359516143798828s
Interlinking | Calculation of Degree of Connection for Pleiades took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Pleiades took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Pleiades took 7.915496826171875e-05s
Believability | Calculation of trust value for Pleiades took 1.3113021850585938e-05s
INFO | --- Analysis for pleiades took 14.648070812225342s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.315376281738281e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.2533149719238281s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 2.86102294921875e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.152557373046875e-06s
INFO | --- Analysis for podorozhnyk took 3.6262552738189697s
Availability | SPARQL endpoint availability check for Poképédia took 4.291534423828125e-05s
Availability | VoID file availability check for Poképédia took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2583754062652588s
Reputation | Calculation of the PageRank for Poképédia took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0010805130004882812s
Interlinking | Calculation of Clustering coefficient for Poképédia took 8.535385131835938e-05s
Believability | Calculation of trust value for Poképédia took 7.152557373046875e-06s
INFO | --- Analysis for pokepedia-fr took 2.658905506134033s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 5.435943603515625e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.2884635925292969s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.02079629898071289s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.62939453125e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.2159347534179688e-05s
INFO | --- Analysis for polymath-virtual-library took 6.042808532714844s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.7718796730041504s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2747373580932617s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.023669719696044922s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3828277587890625e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.3909759521484375e-06s
INFO | --- Analysis for portuguese_prisons_releases took 11.27378511428833s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.1484832763671875e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.27890706062316895s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 2.9325485229492188e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 8.344650268554688e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.9398488998413086s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 0.0004048347473144531s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2993464469909668s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 2.956390380859375e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 8.106231689453125e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 3.0029637813568115s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 4.220008850097656e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.2747020721435547s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.021894454956054688s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 2.9802322387695312e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 8.106231689453125e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.9419965744018555s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.315376281738281e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2739229202270508s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.021363019943237305s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.075599670410156e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.976436138153076s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.27544140815734863s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 2.86102294921875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.942676544189453s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 5.4836273193359375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.2851288318634033s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.02074408531188965s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.075599670410156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.967804193496704s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.100799560546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0003464221954345703s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.2829608917236328s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.893094778060913s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.291534423828125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.2832045555114746s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.9666032791137695s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 5.459785461425781e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0003058910369873047s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.24498605728149414s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020678997039794922s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.918236255645752s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.26299428939819336s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.075599670410156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.874833822250366s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.26421380043029785s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.8630566596984863s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 6.556510925292969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.25464749336242676s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 3.0037481784820557s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.28241944313049316s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 9.298324584960938e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.9080331325531006s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2798147201538086s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.9397592544555664s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 5.459785461425781e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2601468563079834s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 1.1444091796875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.9305338859558105s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.839897155761719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2840747833251953s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.02054119110107422s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 1.2159347534179688e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.903576135635376s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.2812459468841553s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.8995161056518555s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.27950310707092285s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.9504828453063965s
Availability | SPARQL endpoint availability check for prefix.cc took 4.220008850097656e-05s
Availability | VoID file availability check for prefix.cc took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.24147248268127441s
Reputation | Calculation of the PageRank for prefix.cc took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.6716461181640625e-05s
Believability | Calculation of trust value for prefix.cc took 7.62939453125e-06s
INFO | --- Analysis for prefix-cc took 3.1680071353912354s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 2.210385322570801s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.25887179374694824s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.792213439941406e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 9.427973985671997s
Availability | SPARQL endpoint availability check for PreLex took 4.39520788192749s
Availability | VoID file availability check for PreLex took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for PreLex took 0.255767822265625s
Reputation | Calculation of the PageRank for PreLex took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for PreLex took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.43865966796875e-05s
Believability | Calculation of trust value for PreLex took 1.1444091796875e-05s
INFO | --- Analysis for prelex took 12.647704124450684s
Availability | SPARQL endpoint availability check for Prelinger Archives took 9.777195453643799s
Availability | VoID file availability check for Prelinger Archives took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.2541666030883789s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020661592483520508s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.0517578125e-05s
Believability | Calculation of trust value for Prelinger Archives took 6.198883056640625e-06s
INFO | --- Analysis for prelinger_archives took 26.620030879974365s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.46799635887145996s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.2647688388824463s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 5.078315734863281e-05s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 6.9141387939453125e-06s
INFO | --- Analysis for premon took 5.031243085861206s
Availability | SPARQL endpoint availability check for Previsible took 4.3392181396484375e-05s
Availability | VoID file availability check for Previsible took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Previsible took 0.27344799041748047s
Reputation | Calculation of the PageRank for Previsible took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Previsible took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.1920928955078125e-05s
Believability | Calculation of trust value for Previsible took 6.67572021484375e-06s
INFO | --- Analysis for Previsible took 2.433563470840454s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 6.771087646484375e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.26065802574157715s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020915508270263672s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.91278076171875e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 8.106231689453125e-06s
INFO | --- Analysis for princeton-library-findingaids took 4.790154218673706s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.5415351390838623s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.264268159866333s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.02108168601989746s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for PrinParLat took 4.234955310821533s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.5405867099761963s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.2642993927001953s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.463859558105469e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.106231689453125e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.3635365962982178s
Availability | SPARQL endpoint availability check for Prior Panel took 4.315376281738281e-05s
Availability | VoID file availability check for Prior Panel took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.262587308883667s
Reputation | Calculation of the PageRank for Prior Panel took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.2901763916015625e-05s
Believability | Calculation of trust value for Prior Panel took 6.67572021484375e-06s
INFO | --- Analysis for Prior_Panel took 2.3766839504241943s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.2438507080078125e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.283400297164917s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.0994415283203125e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 8.58306884765625e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.9796857833862305s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 8.153915405273438e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.266970157623291s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0008435249328613281s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.743171691894531e-05s
Believability | Calculation of trust value for Procomún SPARQL took 8.344650268554688e-06s
INFO | --- Analysis for procomun-sparql took 2.9020228385925293s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.9114227294921875e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.3173084259033203s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.0279159545898438e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 7.62939453125e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.999047040939331s
Availability | SPARQL endpoint availability check for ProductDB took 4.196570634841919s
Availability | VoID file availability check for ProductDB took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2514481544494629s
Reputation | Calculation of the PageRank for ProductDB took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.390975952148438e-05s
Believability | Calculation of trust value for ProductDB took 1.1682510375976562e-05s
INFO | --- Analysis for productdb took 7.990593433380127s
Availability | SPARQL endpoint availability check for Product Types Ontology took 8.153915405273438e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.257920503616333s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.557868957519531e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for productontology took 3.372169256210327s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.2438507080078125e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.26880526542663574s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010251998901367188s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 8.808790445327759s
Availability | SPARQL endpoint availability check for provenanceweb took 0.054351091384887695s
Availability | VoID file availability check for provenanceweb took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.4222428798675537s
Reputation | Calculation of the PageRank for provenanceweb took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 8.082389831542969e-05s
Believability | Calculation of trust value for provenanceweb took 7.152557373046875e-06s
INFO | --- Analysis for provenanceweb took 71.20584535598755s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.172325134277344e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2497243881225586s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020248889923095703s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010013580322265625s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.7404556274414062e-05s
INFO | --- Analysis for proyectoapadrina took 9.326143503189087s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.578824996948242s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008392333984375s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.27817869186401367s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 4.124641418457031e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 5.9604644775390625e-06s
INFO | --- Analysis for pscs-catalogue took 125.83099150657654s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.506111145019531e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.2711803913116455s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.343292236328125e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 6.9141387939453125e-06s
INFO | --- Analysis for psh-subject-headings took 3.171623706817627s
Availability | SPARQL endpoint availability check for Depression took 0.31861233711242676s
Availability | VoID file availability check for Depression took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Depression took 0.27944159507751465s
Reputation | Calculation of the PageRank for Depression took 0.02046346664428711s
Interlinking | Calculation of Degree of Connection for Depression took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Depression took 2.8848648071289062e-05s
Believability | Calculation of trust value for Depression took 9.059906005859375e-06s
INFO | --- Analysis for Psychology took 2.759768009185791s
Availability | SPARQL endpoint availability check for PubChem RDF took 5.507469177246094e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.2382214069366455s
Reputation | Calculation of the PageRank for PubChem RDF took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 3.910064697265625e-05s
Believability | Calculation of trust value for PubChem RDF took 7.152557373046875e-06s
INFO | --- Analysis for PubChem_RDF took 5.8479533195495605s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 8.153915405273438e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2719132900238037s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 2.8133392333984375e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 8.106231689453125e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.9817094802856445s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.7379047870635986s
Availability | VoID file availability check for Public Spending in Greece took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.28321075439453125s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020789384841918945s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.082389831542969e-05s
Believability | Calculation of trust value for Public Spending in Greece took 6.4373016357421875e-06s
INFO | --- Analysis for public-spending-in-greece took 8.352659225463867s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.172325134277344e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.26916050910949707s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.9325485229492188e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 7.867813110351562e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.884336471557617s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.26002001762390137s
Availability | VoID file availability check for Publications Office Authority tables took 0.0008008480072021484s
Extra | Recovery of all triples for Publications Office Authority tables took 114.44197630882263s
Performance | Total latancy measurement for Publications Office Authority tables took 0.6217443943023682s
Amount of data | Number of triples check for Publications Office Authority tables took 0.6455707550048828s
Interoperability | New terms check for Publications Office Authority tables took 11.864777565002441s
Versatility | Languages check for Publications Office Authority tables took 300.0274257659912s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 2.6602165699005127s
Security | Check HTTPS for Publications Office Authority tables took 0.31412220001220703s
Interpretability | RDF structures check for Publications Office Authority tables took 0.641251802444458s
Versatility | Serialization formats check for Publications Office Authority tables took 2.8048086166381836s
Availability | RDF dump link check for Publications Office Authority tables took 0.33617353439331055s
License | MR license check for Publications Office Authority tables took 0.2691481113433838s
License | HR license check for Publications Office Authority tables took 300.0576148033142s
Amount of data | Number of property check for Publications Office Authority tables took 0.17334342002868652s
Understandability | Number of label check for Publications Office Authority tables took 1.034665584564209s
Understandability | URI regex check for Publications Office Authority tables took 0.4366495609283447s
Understandability | Vocabs check for Publications Office Authority tables took 0.1251969337463379s
Verifiability | Authors check for Publications Office Authority tables took 0.11047697067260742s
Verifiability | Publishers check for Publications Office Authority tables took 0.2620854377746582s
Performance | Throughput check for Publications Office Authority tables took 10.5065336227417s
Amount of data | Check the number of entities for Publications Office Authority tables took 0.00010228157043457031s
Verifiability | Contribs. check for Publications Office Authority tables took 0.13456487655639648s
Interlinking | sameAs chians check for Publications Office Authority tables took 1.0492427349090576s
Interlinking | skos check for Publications Office Authority tables took 0.41867828369140625s
Interlinking | skos check for Publications Office Authority tables took 0.12874555587768555s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.3332681655883789s
Currency | Creation date check for Publications Office Authority tables took 0.2828185558319092s
Currency | Modification date check for Publications Office Authority tables took 0.23175430297851562s
Rep.Conc. | URIs length for Publications Office Authority tables took 171.9199733734131s
Interoperability | New vocabularies check for Publications Office Authority tables took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.1458418369293213s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.1875777244567871s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.14499282836914062s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 36.230494022369385s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.170875072479248s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.616879463195801s
Consistency | Disjoint class check for Publications Office Authority tables took 0.14740848541259766s
Consistency | Check Misplaced properties for Publications Office Authority tables took 53.722041845321655s
Consistency | Misplaced classes for Publications Office Authority tables took 8.374948501586914s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 38.035778522491455s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.449704647064209s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 54.94132328033447s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.0202198028564453s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.42394423484802246s
Security | Sign check for Publications Office Authority tables took 0.10999345779418945s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 9.12906551361084s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.2024030685424805s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.021388530731201172s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0009756088256835938s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 5.91278076171875e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.9073486328125e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 5.7220458984375e-06s
INFO | --- Analysis for publications_office_authority_tables took 14996.593552589417s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 6.437301635742188e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.7881073951721191s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.020597219467163086s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.000978708267211914s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.62396240234375e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 7.3909759521484375e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 5.218204736709595s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.3392181396484375e-05s
Availability | VoID file availability check for QBOAirbase took 0.00078582763671875s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.29293251037597656s
Reputation | Calculation of the PageRank for QBOAirbase took 0.020322799682617188s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.891654968261719e-05s
Believability | Calculation of trust value for QBOAirbase took 6.9141387939453125e-06s
INFO | --- Analysis for qboairbase took 137.49895763397217s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 0.0001595020294189453s
Availability | VoID file availability check for qualitywebdata.org took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.25272178649902344s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 2.7894973754882812e-05s
Believability | Calculation of trust value for qualitywebdata.org took 7.62939453125e-06s
INFO | --- Analysis for qualitywebdata-org took 3.482635021209717s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.3392181396484375e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.7201142311096191s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.020261049270629883s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.9087066650390625e-05s
Believability | Calculation of trust value for Qualité de l'air took 6.9141387939453125e-06s
INFO | --- Analysis for Qualité_de_l'air took 4.2374207973480225s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.4345855712890625e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.3923494815826416s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.02061295509338379s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.457069396972656e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 5.7220458984375e-06s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 54.69697093963623s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.4909489154815674s
Availability | VoID file availability check for Querolus in LiLa took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.2666630744934082s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Querolus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for Querolus took 6.305315256118774s
Availability | SPARQL endpoint availability check for Quotations Book took 4.553794860839844e-05s
Availability | VoID file availability check for Quotations Book took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.2512226104736328s
Reputation | Calculation of the PageRank for Quotations Book took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.123283386230469e-05s
Believability | Calculation of trust value for Quotations Book took 7.3909759521484375e-06s
INFO | --- Analysis for quotations_book took 3.394685745239258s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 5.125999450683594e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.27283763885498047s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02079176902770996s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.152557373046875e-06s
INFO | --- Analysis for r4r took 2.9453542232513428s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1253137588500977s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.000843048095703125s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.275634765625s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020381927490234375s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.839897155761719e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.3909759521484375e-06s
INFO | --- Analysis for racai-legalnero took 4.8052544593811035s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 8.0108642578125e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.28003501892089844s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.2901763916015625e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 7.3909759521484375e-06s
INFO | --- Analysis for racai-llod-corola-we took 2.9281344413757324s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 56.25613760948181s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.2527287006378174s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 4.696846008300781e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-parseme-ro took 59.28147339820862s
Availability | SPARQL endpoint availability check for RoLEX took 51.33684468269348s
Availability | VoID file availability check for RoLEX took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for RoLEX took 0.25408482551574707s
Reputation | Calculation of the PageRank for RoLEX took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.337860107421875e-05s
Believability | Calculation of trust value for RoLEX took 9.775161743164062e-06s
INFO | --- Analysis for racai-llod-rolex took 56.11066269874573s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2646503448486328s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.021293163299560547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 2.9802322387695312e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 6.416977643966675s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.744529724121094e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.2502305507659912s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.956390380859375e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.1205673217773438e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 3.3985464572906494s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.506111145019531e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.266772985458374s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0009634494781494141s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.2901763916015625e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.5860655307769775s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.291534423828125e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2496480941772461s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.8848648071289062e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.7079989910125732s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.41680192947387695s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0007660388946533203s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.28234195709228516s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 3.123283386230469e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-rtasc took 5.860267877578735s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 1.0701279640197754s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.26642775535583496s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 3.0994415283203125e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-simonero took 4.574334383010864s
Availability | SPARQL endpoint availability check for Rådata nå! took 1.844886302947998s
Availability | VoID file availability check for Rådata nå! took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.27669811248779297s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.630752563476562e-05s
Believability | Calculation of trust value for Rådata nå! took 6.9141387939453125e-06s
INFO | --- Analysis for radatana took 6.10763144493103s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.4345855712890625e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.24987053871154785s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.719329833984375e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 7.152557373046875e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 16.62709879875183s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.291534423828125e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.262493371963501s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 2.9325485229492188e-05s
Believability | Calculation of trust value for Raphael Research Resource took 7.3909759521484375e-06s
INFO | --- Analysis for raphaelresearchresource took 2.9532251358032227s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.265211582183838s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.27765512466430664s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.266334533691406e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 6.67572021484375e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 27.56273627281189s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.84832859039307s
Availability | VoID file availability check for Polish LGU financial statements took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.25789856910705566s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.02089405059814453s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 4.673004150390625e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 8.344650268554688e-06s
INFO | --- Analysis for Rb_PL_LGU took 667.7991816997528s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.2622108459472656s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 2.9802322387695312e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 4.114966630935669s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.2494351863861084s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 4.198422908782959s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.482269287109375e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.25987768173217773s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.02100682258605957s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.314018249511719e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 4.258936405181885s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 8.320808410644531e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.2582876682281494s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020641565322875977s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 3.170967102050781e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 2.883535385131836s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 8.606910705566406e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.2515714168548584s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.0209653377532959s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.2901763916015625e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 8.821487426757812e-06s
INFO | --- Analysis for rcahmw-periods-list took 3.356018543243408s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.458427429199219e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2491164207458496s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.027713537216186523s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0014750957489013672s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 0.00013446807861328125s
Believability | Calculation of trust value for RDF Book Mashup took 1.0728836059570312e-05s
INFO | --- Analysis for rdf-book-mashup took 3.3552727699279785s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.57763671875e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.26577234268188477s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010037422180175781s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 6.67572021484375e-06s
INFO | --- Analysis for rdfize-lastfm took 2.505814790725708s
Availability | SPARQL endpoint availability check for RDFLicense took 261.77090072631836s
Availability | VoID file availability check for RDFLicense took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.26027750968933105s
Reputation | Calculation of the PageRank for RDFLicense took 0.021126270294189453s
Interlinking | Calculation of Degree of Connection for RDFLicense took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0008692741394042969s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 5.0067901611328125e-05s
Believability | Calculation of trust value for RDFLicense took 7.867813110351562e-06s
INFO | --- Analysis for rdflicense took 537.2166380882263s
Availability | SPARQL endpoint availability check for RDFohloh took 4.38690185546875e-05s
Availability | VoID file availability check for RDFohloh took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.34549570083618164s
Reputation | Calculation of the PageRank for RDFohloh took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for RDFohloh took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 8.940696716308594e-05s
Believability | Calculation of trust value for RDFohloh took 6.9141387939453125e-06s
INFO | --- Analysis for rdfohloh took 8.078901529312134s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.6361889839172363s
Availability | VoID file availability check for Reactome RDF took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.7186152935028076s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.600120544433594e-05s
Believability | Calculation of trust value for Reactome RDF took 7.152557373046875e-06s
INFO | --- Analysis for reactome-rdf took 4.754438400268555s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.21432065963745117s
Availability | VoID file availability check for Rechtspraak.nl took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.2426302433013916s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.059906005859375e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 5.9604644775390625e-06s
INFO | --- Analysis for rechtspraak took 2.605292320251465s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.315376281738281e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2631382942199707s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.0203702449798584s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 9.036064147949219e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.4543533325195312e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 7.895093679428101s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.1086125373840332s
Availability | VoID file availability check for reference.data.gov.uk took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2623763084411621s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.000152587890625s
Believability | Calculation of trust value for reference.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.620823621749878s
Availability | SPARQL endpoint availability check for Regiony took 5.7697296142578125e-05s
Availability | VoID file availability check for Regiony took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Regiony took 0.28902244567871094s
Reputation | Calculation of the PageRank for Regiony took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for Regiony took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Regiony took 2.9087066650390625e-05s
Believability | Calculation of trust value for Regiony took 8.106231689453125e-06s
INFO | --- Analysis for regiony took 3.120429754257202s
Availability | SPARQL endpoint availability check for RELD took 262.6564497947693s
Availability | VoID file availability check for RELD took 0.0008227825164794922s
Completeness | Calculation of interlinking completeness for RELD took 0.2778010368347168s
Reputation | Calculation of the PageRank for RELD took 0.02080368995666504s
Interlinking | Calculation of Degree of Connection for RELD took 1.52587890625e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for RELD took 3.647804260253906e-05s
Believability | Calculation of trust value for RELD took 7.62939453125e-06s
INFO | --- Analysis for RELD took 537.2987053394318s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.2160015106201172s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005123615264892578s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.7422175407409668s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.6590607166290283s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.372420072555542s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.7322998046875s
Versatility | Languages check for Repository for Linked Open Archival Data took 5.824587821960449s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.2799460887908936s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.5615372657775879s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.3251166343688965s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.3175544738769531s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.19353818893432617s
License | MR license check for Repository for Linked Open Archival Data took 0.43274855613708496s
License | HR license check for Repository for Linked Open Archival Data took 7.984272718429565s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.16610002517700195s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.93837571144104s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.5194332599639893s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.13740897178649902s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.2168750762939453s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.21385741233825684s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.587012529373169s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 7.224082946777344e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.07161402702331543s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.15103864669799805s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.2141275405883789s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.2846965789794922s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.20427298545837402s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.25893330574035645s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.3518192768096924s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.647859811782837s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.14101648330688477s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.19879555702209473s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.1485588550567627s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 1.1381261348724365s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.029116153717041016s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028375625610351562s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.1815638542175293s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.978865385055542s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.20553207397460938s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.7444465160369873s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.255408525466919s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.126508951187134s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.030833005905151367s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.15534377098083496s
Security | Sign check for Repository for Linked Open Archival Data took 0.5156104564666748s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1145.2047173976898s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.872025728225708s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.020836830139160156s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 4.76837158203125e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 7.3909759521484375e-06s
INFO | --- Analysis for reload took 1265.9227843284607s
Availability | SPARQL endpoint availability check for Land use merced dataset took 5.555152893066406e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.6936676502227783s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.0517578125e-05s
Believability | Calculation of trust value for Land use merced dataset took 6.67572021484375e-06s
INFO | --- Analysis for remote_Sensing took 14.458269596099854s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.896599531173706s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.6819114685058594s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.5299530029296875e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 4.76837158203125e-06s
INFO | --- Analysis for renewable_energy_generators took 16.054168939590454s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.08302164077758789s
Availability | VoID file availability check for research.data.gov.uk took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.23077893257141113s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.02097916603088379s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.584426879882812e-05s
Believability | Calculation of trust value for research.data.gov.uk took 6.198883056640625e-06s
INFO | --- Analysis for research-data-gov-uk took 2.7757270336151123s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 4.267692565917969e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.2892303466796875s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.1948089599609375e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 8.106231689453125e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 3.7557082176208496s
Availability | SPARQL endpoint availability check for Restaurantes took 4.315376281738281e-05s
Availability | VoID file availability check for Restaurantes took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.30759310722351074s
Reputation | Calculation of the PageRank for Restaurantes took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for Restaurantes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Restaurantes took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 2.765655517578125e-05s
Believability | Calculation of trust value for Restaurantes took 7.62939453125e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.8548672199249268s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.291534423828125e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.2579529285430908s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.02094435691833496s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.628036499023438e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 7.867813110351562e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 5.177946329116821s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.13881492614746094s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0004069805145263672s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.284259557723999s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.147125244140625e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 8.58306884765625e-06s
INFO | --- Analysis for revistas_turismo took 2.578444242477417s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.3000824451446533s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2620828151702881s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.021108627319335938s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011682510375976562s
Believability | Calculation of trust value for Revyu.com - Review Anything took 7.62939453125e-06s
INFO | --- Analysis for revyu took 2.693007230758667s
Availability | SPARQL endpoint availability check for sdafsadf took 0.41094088554382324s
Availability | VoID file availability check for sdafsadf took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.38010287284851074s
Reputation | Calculation of the PageRank for sdafsadf took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 2.9087066650390625e-05s
Believability | Calculation of trust value for sdafsadf took 8.106231689453125e-06s
INFO | --- Analysis for rgsdfg took 3.7341701984405518s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.38690185546875e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.2850306034088135s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.410743713378906e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 6.9141387939453125e-06s
INFO | --- Analysis for riese took 2.5211524963378906s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.291534423828125e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.2608633041381836s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.0205996036529541s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 6.9141387939453125e-06s
INFO | --- Analysis for rijksmuseum took 2.9243369102478027s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.9482650756835938s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.26174020767211914s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020255088806152344s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.1484832763671875e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 6.9141387939453125e-06s
INFO | --- Analysis for rism took 3.8881046772003174s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.1650857925415039s
Availability | VoID file availability check for RISM Authority data took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.28426218032836914s
Reputation | Calculation of the PageRank for RISM Authority data took 0.021036148071289062s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.458427429199219e-05s
Believability | Calculation of trust value for RISM Authority data took 7.3909759521484375e-06s
INFO | --- Analysis for rism-authorities took 3.1617774963378906s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0003483295440673828s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.27906179428100586s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for engineering equipment ontology took 6.9141387939453125e-06s
INFO | --- Analysis for rk took 2.444093942642212s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.11619758605957031s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.2504420280456543s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002276897430419922s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.530280590057373s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.035988569259643555s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.2859644889831543s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.020221710205078125s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0009779930114746094s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001544952392578125s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.503117322921753s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0501251220703125s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.27230262756347656s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020586490631103516s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00021123886108398438s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.455357789993286s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.04293656349182129s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.27204418182373047s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020859718322753906s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00017333030700683594s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.536973714828491s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.04888010025024414s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.2570457458496094s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020154476165771484s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015592575073242188s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.4587783813476562s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.05132889747619629s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2627561092376709s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.62396240234375e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.4320878982543945s
Availability | SPARQL endpoint availability check for crm took 4.172325134277344e-05s
Availability | VoID file availability check for crm took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for crm took 0.25219225883483887s
Reputation | Calculation of the PageRank for crm took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for crm took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for crm took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for crm took 2.956390380859375e-05s
Believability | Calculation of trust value for crm took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.8534786701202393s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.04330706596374512s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.25150442123413086s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011920928955078125s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.4484400749206543s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04233717918395996s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.2525942325592041s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.030632019042969e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.4006080627441406s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.04143333435058594s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.23822259902954102s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002391338348388672s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.453890085220337s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04196667671203613s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.2755413055419922s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.319450378417969e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.467940330505371s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.04082131385803223s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2739114761352539s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020205259323120117s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.870529174804688e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.5296216011047363s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.051384925842285156s
Availability | VoID file availability check for digitaleconomy took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.2688412666320801s
Reputation | Calculation of the PageRank for digitaleconomy took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.9087066650390625e-05s
Believability | Calculation of trust value for digitaleconomy took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.469487428665161s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.044852256774902344s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0003712177276611328s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2602403163909912s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.0001544952392578125s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.5601344108581543s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.045151710510253906s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.26521992683410645s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.291534423828125e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.7560386657714844s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.2438507080078125e-05s
Availability | VoID file availability check for enaktingpsi took 0.0002961158752441406s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.2904071807861328s
Reputation | Calculation of the PageRank for enaktingpsi took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 2.765655517578125e-05s
Believability | Calculation of trust value for enaktingpsi took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.980137348175049s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.04097104072570801s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.2817666530609131s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00019931793212890625s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.4795401096343994s
Availability | SPARQL endpoint availability check for epsrc took 0.034102439880371094s
Availability | VoID file availability check for epsrc took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for epsrc took 0.26485419273376465s
Reputation | Calculation of the PageRank for epsrc took 0.02030467987060547s
Interlinking | Calculation of Degree of Connection for epsrc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for epsrc took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.53131103515625e-05s
Believability | Calculation of trust value for epsrc took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.4446327686309814s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.04157853126525879s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.25000905990600586s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.748603820800781e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-era took 2.436410903930664s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.04347348213195801s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0003581047058105469s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.26631999015808105s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 9.942054748535156e-05s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.46327543258667s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.076957702636719e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.25793957710266113s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 2.8133392333984375e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 6.008148193359375e-05s
INFO | --- Analysis for rkb-explorer-foreign took 2.8930017948150635s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.04092741012573242s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.25461411476135254s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0009810924530029297s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.942054748535156e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.514303207397461s
Availability | SPARQL endpoint availability check for fun took 0.04722881317138672s
Availability | VoID file availability check for fun took 0.0003631114959716797s
Completeness | Calculation of interlinking completeness for fun took 0.2675354480743408s
Reputation | Calculation of the PageRank for fun took 0.020269393920898438s
Interlinking | Calculation of Degree of Connection for fun took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for fun took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for fun took 7.414817810058594e-05s
Believability | Calculation of trust value for fun took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.394012689590454s
Availability | SPARQL endpoint availability check for gdlc took 0.047318458557128906s
Availability | VoID file availability check for gdlc took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for gdlc took 0.2748143672943115s
Reputation | Calculation of the PageRank for gdlc took 0.0209963321685791s
Interlinking | Calculation of Degree of Connection for gdlc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for gdlc took 7.2479248046875e-05s
Believability | Calculation of trust value for gdlc took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.506427526473999s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.042705535888671875s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.24664092063903809s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020165681838989258s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00010943412780761719s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.5327086448669434s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.04844498634338379s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2637507915496826s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00013780593872070312s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.4905214309692383s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.04965400695800781s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.24564576148986816s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00014472007751464844s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.496189594268799s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.045626163482666016s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.2758193016052246s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.365776062011719e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.4641003608703613s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.049791574478149414s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.2521824836730957s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020321130752563477s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.367134094238281e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.508523464202881s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.03681159019470215s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2817037105560303s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020472288131713867s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.291534423828125e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.448669910430908s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.049237728118896484s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2807273864746094s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0001633167266845703s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.47139835357666s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.04465031623840332s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.27707791328430176s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00014901161193847656s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.4894042015075684s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.03510689735412598s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2809934616088867s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.079673767089844e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.480518341064453s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.04330587387084961s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.27672743797302246s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015687942504882812s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.483999013900757s
Availability | SPARQL endpoint availability check for notube took 0.04163837432861328s
Availability | VoID file availability check for notube took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for notube took 0.24706482887268066s
Reputation | Calculation of the PageRank for notube took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for notube took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for notube took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for notube took 3.886222839355469e-05s
Believability | Calculation of trust value for notube took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.430074691772461s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.04096531867980957s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.25739336013793945s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020911216735839844s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00013709068298339844s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.481426477432251s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.05762052536010742s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.25060105323791504s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015735626220703125s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.53010892868042s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.029273986816406e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.2580394744873047s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.8220598697662354s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.03570103645324707s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.2749466896057129s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.271766662597656e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-os took 2.523829936981201s
Availability | SPARQL endpoint availability check for photos took 0.04496645927429199s
Availability | VoID file availability check for photos took 0.00040793418884277344s
Completeness | Calculation of interlinking completeness for photos took 0.2667267322540283s
Reputation | Calculation of the PageRank for photos took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for photos took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for photos took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for photos took 7.176399230957031e-05s
Believability | Calculation of trust value for photos took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.439683437347412s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.04094886779785156s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.29128384590148926s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.02029132843017578s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011086463928222656s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.4226834774017334s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.041774749755859375s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0010402202606201172s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2640717029571533s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.02113938331604004s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00020384788513183594s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.4336297512054443s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.041310787200927734s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.25864362716674805s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0001399517059326172s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.4525299072265625s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.04355025291442871s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.24103331565856934s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.298324584960938e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.4001638889312744s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.05254364013671875s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2803077697753906s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0001239776611328125s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.5587258338928223s
Availability | SPARQL endpoint availability check for roni took 0.047890424728393555s
Availability | VoID file availability check for roni took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for roni took 0.24425697326660156s
Reputation | Calculation of the PageRank for roni took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for roni took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for roni took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for roni took 2.7894973754882812e-05s
Believability | Calculation of trust value for roni took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.4475185871124268s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0429387092590332s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.2607429027557373s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020386457443237305s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00021886825561523438s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.4414329528808594s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.054154396057128906s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.2559201717376709s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010943412780761719s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.3845646381378174s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.048987627029418945s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.2626931667327881s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.846687316894531e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 2.482877492904663s
Availability | SPARQL endpoint availability check for webconf took 0.04073929786682129s
Availability | VoID file availability check for webconf took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for webconf took 0.24980735778808594s
Reputation | Calculation of the PageRank for webconf took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for webconf took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010704994201660156s
Believability | Calculation of trust value for webconf took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-webconf took 12.777383089065552s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.04110455513000488s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.26743483543395996s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0008633136749267578s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.367134094238281e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.403125286102295s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04638409614562988s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2675435543060303s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002105236053466797s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.4987332820892334s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.04089212417602539s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.2621030807495117s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.226799011230469e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.4689486026763916s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.1961669921875e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.25144147872924805s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 2.6702880859375e-05s
Believability | Calculation of trust value for RKB Explorer Data took 6.67572021484375e-06s
INFO | --- Analysis for rkb_explorer_data took 2.8831899166107178s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.48481225967407227s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.27193164825439453s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.749961853027344e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 8.344650268554688e-06s
INFO | --- Analysis for roceeh-road took 3.7845723628997803s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.38690185546875e-05s
Availability | VoID file availability check for The Rosetta Project took 0.000274658203125s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.26729416847229004s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 2.956390380859375e-05s
Believability | Calculation of trust value for The Rosetta Project took 8.106231689453125e-06s
INFO | --- Analysis for rosetta-project took 2.8883016109466553s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.38690185546875e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.24913430213928223s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.021999597549438477s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0010294914245605469s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.528594970703125e-05s
Believability | Calculation of trust value for ontology terrorist attack took 7.152557373046875e-06s
INFO | --- Analysis for ROSHANI took 3.564300298690796s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 5.5789947509765625e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.24913978576660156s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.021528959274291992s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0009911060333251953s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.695487976074219e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 7.152557373046875e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.333238363265991s
Availability | SPARQL endpoint availability check for x took 4.458427429199219e-05s
Availability | VoID file availability check for x took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for x took 0.27460217475891113s
Reputation | Calculation of the PageRank for x took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for x took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for x took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for x took 2.6941299438476562e-05s
Believability | Calculation of trust value for x took 6.67572021484375e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.3289475440979004s
Availability | SPARQL endpoint availability check for Rpm Find took 4.0531158447265625e-05s
Availability | VoID file availability check for Rpm Find took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.27272748947143555s
Reputation | Calculation of the PageRank for Rpm Find took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for Rpm Find took 3.147125244140625e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 2.8133392333984375e-05s
Believability | Calculation of trust value for Rpm Find took 6.9141387939453125e-06s
INFO | --- Analysis for rpm_find took 2.8747711181640625s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.458427429199219e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.25034117698669434s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.03164315223693848s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0012705326080322266s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 9.608268737792969e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 7.152557373046875e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.7169668674468994s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.315376281738281e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.26151394844055176s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.104873657226562e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 7.152557373046875e-06s
INFO | --- Analysis for rubentaelman took 3.0434582233428955s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.315376281738281e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2687039375305176s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02109694480895996s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.511543273925781e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 7.152557373046875e-06s
INFO | --- Analysis for rubenverborgh took 3.3468050956726074s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.44035720825195s
Availability | VoID file availability check for Russian Universities Specialities took 0.0009086132049560547s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.6953868865966797s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 3.9577484130859375e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.1920928955078125e-05s
INFO | --- Analysis for russian-universities-specialities took 677.6399943828583s
Availability | SPARQL endpoint availability check for RuThes Cloud took 0.00010395050048828125s
Availability | VoID file availability check for RuThes Cloud took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.3059663772583008s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.02099752426147461s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.743171691894531e-05s
Believability | Calculation of trust value for RuThes Cloud took 8.58306884765625e-06s
INFO | --- Analysis for ruthes took 4.358774662017822s
Availability | SPARQL endpoint availability check for RxNorm took 4.553794860839844e-05s
Availability | VoID file availability check for RxNorm took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for RxNorm took 0.2782468795776367s
Reputation | Calculation of the PageRank for RxNorm took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for RxNorm took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RxNorm took 0.0007977485656738281s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.504753112792969e-05s
Believability | Calculation of trust value for RxNorm took 8.58306884765625e-06s
INFO | --- Analysis for rxnorm took 3.3441100120544434s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.3455822467803955s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0007507801055908203s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.2703559398651123s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.075599670410156e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 6.4373016357421875e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 9.912254333496094s
Availability | SPARQL endpoint availability check for SALDO took 5.602836608886719e-05s
Availability | VoID file availability check for SALDO took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for SALDO took 0.2587554454803467s
Reputation | Calculation of the PageRank for SALDO took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for SALDO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.0040740966796875e-05s
Believability | Calculation of trust value for SALDO took 7.867813110351562e-06s
INFO | --- Analysis for saldo took 2.9045557975769043s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.1579957008361816s
Availability | VoID file availability check for SALDO-RDF took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.24240636825561523s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020856857299804688s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for SALDO-RDF took 7.152557373046875e-06s
INFO | --- Analysis for saldo-rdf took 5.611126184463501s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6642653942108154s
Availability | VoID file availability check for SALDOM-RDF took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.28754639625549316s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.02151966094970703s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0008645057678222656s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.838539123535156e-05s
Believability | Calculation of trust value for SALDOM-RDF took 6.67572021484375e-06s
INFO | --- Analysis for saldom-rdf took 4.7799928188323975s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.363059997558594e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.27408742904663086s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.000102996826171875s
Believability | Calculation of trust value for Salzburgerland DE took 6.4373016357421875e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.0515518188476562s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.410743713378906e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.2820744514465332s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010466575622558594s
Believability | Calculation of trust value for Salzburgerland EN took 5.9604644775390625e-06s
INFO | --- Analysis for salzburgerland-com-en took 2.8085131645202637s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.4345855712890625e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.2669341564178467s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020504236221313477s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010275840759277344s
Believability | Calculation of trust value for Salzburgerland IT took 1.1682510375976562e-05s
INFO | --- Analysis for salzburgerland-com-it took 2.9231855869293213s
Availability | SPARQL endpoint availability check for sameAs.org took 6.67572021484375e-05s
Availability | VoID file availability check for sameAs.org took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.26810359954833984s
Reputation | Calculation of the PageRank for sameAs.org took 0.020437002182006836s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 2.9802322387695312e-05s
Believability | Calculation of trust value for sameAs.org took 8.106231689453125e-06s
INFO | --- Analysis for sameas-org took 2.905109167098999s
Availability | SPARQL endpoint availability check for sandrart.net took 4.363059997558594e-05s
Availability | VoID file availability check for sandrart.net took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.24237298965454102s
Reputation | Calculation of the PageRank for sandrart.net took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.699562072753906e-05s
Believability | Calculation of trust value for sandrart.net took 6.67572021484375e-06s
INFO | --- Analysis for sandrart-net took 3.601273536682129s
Availability | SPARQL endpoint availability check for Taxons  took 0.2922077178955078s
Availability | VoID file availability check for Taxons  took 0.0004901885986328125s
Extra | Recovery of all triples for Taxons  took 23.879497528076172s
Performance | Total latancy measurement for Taxons  took 0.43399882316589355s
Amount of data | Number of triples check for Taxons  took 1.9312877655029297s
Interoperability | New terms check for Taxons  took 1.895967721939087s
Versatility | Languages check for Taxons  took 36.684921741485596s
Interpretability | Number of blank nodes check for Taxons  took 0.9677584171295166s
Security | Check HTTPS for Taxons  took 0.21158409118652344s
Interpretability | RDF structures check for Taxons  took 0.8755507469177246s
Versatility | Serialization formats check for Taxons  took 0.4961206912994385s
Availability | RDF dump link check for Taxons  took 0.2695786952972412s
License | MR license check for Taxons  took 1.235630989074707s
License | HR license check for Taxons  took 1.869976282119751s
Amount of data | Number of property check for Taxons  took 0.11127066612243652s
Understandability | Number of label check for Taxons  took 2.417647361755371s
Understandability | URI regex check for Taxons  took 0.6795239448547363s
Understandability | Vocabs check for Taxons  took 0.20343375205993652s
Verifiability | Authors check for Taxons  took 0.0927116870880127s
Verifiability | Publishers check for Taxons  took 0.08095026016235352s
Performance | Throughput check for Taxons  took 10.452858924865723s
Amount of data | Check the number of entities for Taxons  took 6.866455078125e-05s
Verifiability | Contribs. check for Taxons  took 0.08911442756652832s
Interlinking | sameAs chians check for Taxons  took 0.1386585235595703s
Interlinking | skos check for Taxons  took 0.15446829795837402s
Interlinking | skos check for Taxons  took 0.08463716506958008s
Timeliness | dataset update frequency check for Taxons  took 0.3717172145843506s
Currency | Creation date check for Taxons  took 0.20249247550964355s
Currency | Modification date check for Taxons  took 0.21825170516967773s
Rep.Conc. | URIs length for Taxons  took 9.6206636428833s
Interoperability | New vocabularies check for Taxons  took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.11525535583496094s
Accuracy | Check Functional Property for Taxons  took 0.372020959854126s
Accuracy | Check Inverse Functional Property for Taxons  took 0.30510663986206055s
Accuracy | Check Empty annotation labels for Taxons  took 4.968456745147705s
Accuracy | Check White space in annotation for Taxons  took 0.3048868179321289s
Accuracy | Check Datatype consistency for Taxons  took 0.2613205909729004s
Consistency | Disjoint class check for Taxons  took 0.11336898803710938s
Consistency | Check Misplaced properties for Taxons  took 3.7342796325683594s
Consistency | Misplaced classes for Taxons  took 0.9509396553039551s
Consistency | Check Ontology hijacking for Taxons  took 5.113717555999756s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.2792387008666992s
Consistency | Check Invalid usage of undefined properties for Taxons  took 4.9389142990112305s
Conciseness | Check Extensional conciseness for Taxons  took 0.2836620807647705s
Conciseness | Check Intensional conciseness for Taxons  took 0.19017410278320312s
Security | Sign check for Taxons  took 0.7484424114227295s
Availability | Check URIs Dereferenciability for Taxons  took 1692.5565688610077s
Completeness | Calculation of interlinking completeness for Taxons  took 0.5222740173339844s
Reputation | Calculation of the PageRank for Taxons  took 0.021656274795532227s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Taxons  took 7.843971252441406e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 1.9073486328125e-06s
Believability | Calculation of trust value for Taxons  took 7.62939453125e-06s
INFO | --- Analysis for sandre took 1879.8473951816559s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.9338738918304443s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.2717602252960205s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.075599670410156e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 6.67572021484375e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 8.04928183555603s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 263.9258325099945s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0009264945983886719s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.29284095764160156s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 2.765655517578125e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for santillana_guide_dataset took 670.6810457706451s
Availability | SPARQL endpoint availability check for SATAR test  took 7.677078247070312e-05s
Availability | VoID file availability check for SATAR test  took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.6957135200500488s
Reputation | Calculation of the PageRank for SATAR test  took 0.02094721794128418s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0011167526245117188s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 3.790855407714844e-05s
Believability | Calculation of trust value for SATAR test  took 7.62939453125e-06s
INFO | --- Analysis for SATAR_test took 5.625572919845581s
Availability | SPARQL endpoint availability check for SCBG Data took 21.603495359420776s
Availability | VoID file availability check for SCBG Data took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.2697877883911133s
Reputation | Calculation of the PageRank for SCBG Data took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.082389831542969e-05s
Believability | Calculation of trust value for SCBG Data took 6.67572021484375e-06s
INFO | --- Analysis for SCBG-Data took 54.5625102519989s
Availability | SPARQL endpoint availability check for schema.org took 4.1961669921875e-05s
Availability | VoID file availability check for schema.org took 0.00031280517578125s
Completeness | Calculation of interlinking completeness for schema.org took 0.29113316535949707s
Reputation | Calculation of the PageRank for schema.org took 0.02092432975769043s
Interlinking | Calculation of Degree of Connection for schema.org took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.504753112792969e-05s
Believability | Calculation of trust value for schema.org took 6.4373016357421875e-06s
INFO | --- Analysis for schema-org took 3.4517459869384766s
Availability | SPARQL endpoint availability check for Schemantra took 4.506111145019531e-05s
Availability | VoID file availability check for Schemantra took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for Schemantra took 0.6890335083007812s
Reputation | Calculation of the PageRank for Schemantra took 0.021116018295288086s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.218650817871094e-05s
Believability | Calculation of trust value for Schemantra took 7.62939453125e-06s
INFO | --- Analysis for Schemantra took 3.62075138092041s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.734785556793213s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.23973584175109863s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.4332275390625e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 8.344650268554688e-06s
INFO | --- Analysis for schemapedia took 4.696735382080078s
Availability | SPARQL endpoint availability check for scholarlydata took 4.124641418457031e-05s
Availability | VoID file availability check for scholarlydata took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.24353647232055664s
Reputation | Calculation of the PageRank for scholarlydata took 0.021138906478881836s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 3.170967102050781e-05s
Believability | Calculation of trust value for scholarlydata took 7.867813110351562e-06s
INFO | --- Analysis for scholarlydata took 3.2980518341064453s
Availability | SPARQL endpoint availability check for Scholarometer took 4.267692565917969e-05s
Availability | VoID file availability check for Scholarometer took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.25835490226745605s
Reputation | Calculation of the PageRank for Scholarometer took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for Scholarometer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.893013000488281e-05s
Believability | Calculation of trust value for Scholarometer took 6.198883056640625e-06s
INFO | --- Analysis for scholarometer took 8.212737321853638s
Availability | SPARQL endpoint availability check for Science Commons took 4.1961669921875e-05s
Availability | VoID file availability check for Science Commons took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for Science Commons took 0.29186224937438965s
Reputation | Calculation of the PageRank for Science Commons took 0.02061295509338379s
Interlinking | Calculation of Degree of Connection for Science Commons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Science Commons took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Science Commons took 3.24249267578125e-05s
Believability | Calculation of trust value for Science Commons took 5.9604644775390625e-06s
INFO | --- Analysis for science_commons took 2.943427085876465s
Availability | SPARQL endpoint availability check for ScienceWise took 4.291534423828125e-05s
Availability | VoID file availability check for ScienceWise took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2630438804626465s
Reputation | Calculation of the PageRank for ScienceWise took 0.020798683166503906s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.0994415283203125e-05s
Believability | Calculation of trust value for ScienceWise took 7.152557373046875e-06s
INFO | --- Analysis for sciencewise took 2.943984270095825s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.482269287109375e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.26171398162841797s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.021066904067993164s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.123283386230469e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 5.0067901611328125e-06s
INFO | --- Analysis for scoreboard took 4.772430896759033s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.172325134277344e-05s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.2747929096221924s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.170967102050781e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 6.9141387939453125e-06s
INFO | --- Analysis for SDDEC took 17.03052592277527s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.410743713378906e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.26505160331726074s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 2.765655517578125e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 7.3909759521484375e-06s
INFO | --- Analysis for SDG took 3.323086738586426s
Availability | SPARQL endpoint availability check for sears.com took 4.4345855712890625e-05s
Availability | VoID file availability check for sears.com took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for sears.com took 0.2715945243835449s
Reputation | Calculation of the PageRank for sears.com took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for sears.com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.699562072753906e-05s
Believability | Calculation of trust value for sears.com took 7.152557373046875e-06s
INFO | --- Analysis for sears took 4.630218744277954s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.08313798904418945s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.263505220413208s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.273124694824219e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.245208740234375e-06s
INFO | --- Analysis for sec-rdfabout took 6.255996465682983s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.87500810623169s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.2845745086669922s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.749961853027344e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for secold took 168.42061614990234s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.1484832763671875e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.26129674911499023s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020880699157714844s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.8371810913085938e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 1.2636184692382812e-05s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 3.373460292816162s
Availability | SPARQL endpoint availability check for semanlink took 4.267692565917969e-05s
Availability | VoID file availability check for semanlink took 0.0008616447448730469s
Completeness | Calculation of interlinking completeness for semanlink took 0.27861595153808594s
Reputation | Calculation of the PageRank for semanlink took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for semanlink took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00015044212341308594s
Believability | Calculation of trust value for semanlink took 6.9141387939453125e-06s
INFO | --- Analysis for semanlink took 183.34624338150024s
Availability | SPARQL endpoint availability check for Semantic Library took 4.291534423828125e-05s
Availability | VoID file availability check for Semantic Library took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.702277421951294s
Reputation | Calculation of the PageRank for Semantic Library took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 3.0040740966796875e-05s
Believability | Calculation of trust value for Semantic Library took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-library took 4.272645950317383s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.172325134277344e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.2706279754638672s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 2.9325485229492188e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 6.9141387939453125e-06s
INFO | --- Analysis for semantic-profiling-network took 2.8217341899871826s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.06320714950561523s
Availability | VoID file availability check for Semantic Universe Data took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.25585079193115234s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for Semantic Universe Data took 6.9141387939453125e-06s
INFO | --- Analysis for semantic-universe took 2.5001888275146484s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.438419103622437s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.25919485092163086s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020821571350097656s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00012135505676269531s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-web-dog-food took 83.54441356658936s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.410743713378906e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.2684056758880615s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0013594627380371094s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 5.173683166503906e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.2874603271484375e-05s
INFO | --- Analysis for semantic-web-grundlagen took 3.0407679080963135s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.076957702636719e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2611849308013916s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 2.8133392333984375e-05s
Believability | Calculation of trust value for semantic-web-journal took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-web-journal took 2.9192094802856445s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.76837158203125e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.26827120780944824s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.20159912109375e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 4.291534423828125e-06s
INFO | --- Analysis for semantic-xbrl took 3.421172618865967s
Availability | SPARQL endpoint availability check for Semantic Bible took 4.1484832763671875e-05s
Availability | VoID file availability check for Semantic Bible took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.3118319511413574s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 2.7418136596679688e-05s
Believability | Calculation of trust value for Semantic Bible took 6.4373016357421875e-06s
INFO | --- Analysis for semantic_bible took 2.9303996562957764s
Availability | SPARQL endpoint availability check for SemanticQuran took 6.990056753158569s
Availability | VoID file availability check for SemanticQuran took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.25449562072753906s
Reputation | Calculation of the PageRank for SemanticQuran took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.414817810058594e-05s
Believability | Calculation of trust value for SemanticQuran took 7.152557373046875e-06s
INFO | --- Analysis for semanticquran took 16.659828186035156s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.458427429199219e-05s
Availability | VoID file availability check for SemanticTweet took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.2908315658569336s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02049994468688965s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.2928924560546875e-05s
Believability | Calculation of trust value for SemanticTweet took 6.9141387939453125e-06s
INFO | --- Analysis for semantictweet took 4.044118881225586s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.2438507080078125e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.26825833320617676s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020793676376342773s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0008327960968017578s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.20159912109375e-05s
Believability | Calculation of trust value for semanticweb.org took 7.867813110351562e-06s
INFO | --- Analysis for semanticweb-org took 22.756880521774292s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.06534981727600098s
Availability | VoID file availability check for Semantic CrunchBase took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.24565696716308594s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.628036499023438e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 7.867813110351562e-06s
INFO | --- Analysis for semsol-crunchbase took 2.4794139862060547s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.124641418457031e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.23945403099060059s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 2.8371810913085938e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 7.3909759521484375e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.920607805252075s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2742035388946533s
Availability | VoID file availability check for SentimentWortschatz took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2784757614135742s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.02187633514404297s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0008809566497802734s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.458427429199219e-05s
Believability | Calculation of trust value for SentimentWortschatz took 6.9141387939453125e-06s
INFO | --- Analysis for sentiws took 3.4703269004821777s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.077598333358765s
Availability | VoID file availability check for seoul-bike-data took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.2503702640533447s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.5762786865234375e-05s
Believability | Calculation of trust value for seoul-bike-data took 6.67572021484375e-06s
INFO | --- Analysis for seoul-bike-data took 72.62978315353394s
Availability | SPARQL endpoint availability check for Serendipity took 11.045827865600586s
Availability | VoID file availability check for Serendipity took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Serendipity took 0.25766515731811523s
Reputation | Calculation of the PageRank for Serendipity took 0.02032303810119629s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.224082946777344e-05s
Believability | Calculation of trust value for Serendipity took 7.867813110351562e-06s
INFO | --- Analysis for serendipity took 19.661107778549194s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.267692565917969e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.26949214935302734s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 2.9802322387695312e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 7.62939453125e-06s
INFO | --- Analysis for Sherry_Wine took 2.5910091400146484s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.363059997558594e-05s
Availability | VoID file availability check for Sherry Wine took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.2506399154663086s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.123283386230469e-05s
Believability | Calculation of trust value for Sherry Wine took 7.152557373046875e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.3886773586273193s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.35607171058654785s
Availability | VoID file availability check for Shoah victims? names took 0.0004947185516357422s
Extra | Recovery of all triples for Shoah victims? names took 1.8061559200286865s
Performance | Total latancy measurement for Shoah victims? names took 0.6546494960784912s
Amount of data | Number of triples check for Shoah victims? names took 1.4339814186096191s
Interoperability | New terms check for Shoah victims? names took 1.673149585723877s
Versatility | Languages check for Shoah victims? names took 5.697886943817139s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.295624256134033s
Security | Check HTTPS for Shoah victims? names took 0.554840087890625s
Interpretability | RDF structures check for Shoah victims? names took 0.32137179374694824s
Versatility | Serialization formats check for Shoah victims? names took 0.32909154891967773s
Availability | RDF dump link check for Shoah victims? names took 0.23005294799804688s
License | MR license check for Shoah victims? names took 0.3748934268951416s
License | HR license check for Shoah victims? names took 7.415274381637573s
Amount of data | Number of property check for Shoah victims? names took 0.2918417453765869s
Understandability | Number of label check for Shoah victims? names took 1.091132640838623s
Understandability | URI regex check for Shoah victims? names took 0.5279443264007568s
Understandability | Vocabs check for Shoah victims? names took 0.1679069995880127s
Verifiability | Authors check for Shoah victims? names took 0.22411155700683594s
Verifiability | Publishers check for Shoah victims? names took 0.23589515686035156s
Performance | Throughput check for Shoah victims? names took 10.566526889801025s
Amount of data | Check the number of entities for Shoah victims? names took 5.221366882324219e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.251251220703125s
Interlinking | sameAs chians check for Shoah victims? names took 0.2166152000427246s
Interlinking | skos check for Shoah victims? names took 0.21764349937438965s
Interlinking | skos check for Shoah victims? names took 0.12906384468078613s
Timeliness | dataset update frequency check for Shoah victims? names took 0.2828633785247803s
Currency | Creation date check for Shoah victims? names took 0.4342384338378906s
Currency | Modification date check for Shoah victims? names took 0.2569253444671631s
Rep.Conc. | URIs length for Shoah victims? names took 2.6246254444122314s
Interoperability | New vocabularies check for Shoah victims? names took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.13176226615905762s
Accuracy | Check Functional Property for Shoah victims? names took 0.17821478843688965s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.17224502563476562s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.9158310890197754s
Accuracy | Check White space in annotation for Shoah victims? names took 0.02856135368347168s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.028694629669189453s
Consistency | Disjoint class check for Shoah victims? names took 0.225938081741333s
Consistency | Check Misplaced properties for Shoah victims? names took 2.027257204055786s
Consistency | Misplaced classes for Shoah victims? names took 0.18762898445129395s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.8274080753326416s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.2810533046722412s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.003416061401367s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.029622554779052734s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.28763461112976074s
Security | Sign check for Shoah victims? names took 0.4907057285308838s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1168.4559652805328s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.5137121677398682s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.022450685501098633s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 6.008148193359375e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 2.384185791015625e-06s
Believability | Calculation of trust value for Shoah victims? names took 8.58306884765625e-06s
INFO | --- Analysis for shoah-victims-names took 1277.6380143165588s
Availability | SPARQL endpoint availability check for Person took 4.4345855712890625e-05s
Availability | VoID file availability check for Person took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Person took 0.7095491886138916s
Reputation | Calculation of the PageRank for Person took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for Person took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Person took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Person took 2.8133392333984375e-05s
Believability | Calculation of trust value for Person took 7.152557373046875e-06s
INFO | --- Analysis for Shripriya_Dubey took 3.304746389389038s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.5299530029296875e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.2731926441192627s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 7.3909759521484375e-06s
INFO | --- Analysis for Shutterstock took 2.85563325881958s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.172325134277344e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.2822132110595703s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.02162647247314453s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.00089263916015625s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.218650817871094e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 7.3909759521484375e-06s
INFO | --- Analysis for simile_data_collection took 3.8033673763275146s
Availability | SPARQL endpoint availability check for SIMPLE took 4.363059997558594e-05s
Availability | VoID file availability check for SIMPLE took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.29529404640197754s
Reputation | Calculation of the PageRank for SIMPLE took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for SIMPLE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 5.3882598876953125e-05s
Believability | Calculation of trust value for SIMPLE took 6.67572021484375e-06s
INFO | --- Analysis for simple took 7.750479221343994s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.866000413894653s
Availability | VoID file availability check for SITC-V4 took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.7052323818206787s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.910064697265625e-05s
Believability | Calculation of trust value for SITC-V4 took 5.245208740234375e-06s
INFO | --- Analysis for sitc-v4 took 126.08833765983582s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.315376281738281e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.2705874443054199s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.1484832763671875e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 7.867813110351562e-06s
INFO | --- Analysis for sli_galnet_rdf took 13.326326608657837s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.315376281738281e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.29272890090942383s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.552436828613281e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 6.9141387939453125e-06s
INFO | --- Analysis for slideshare2rdf took 3.0130584239959717s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.291534423828125e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.713186502456665s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.02081775665283203s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 6.9141387939453125e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 3.8008241653442383s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.7829194068908691s
Availability | VoID file availability check for Linked Stage Graph took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.2622871398925781s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 5.173683166503906e-05s
Believability | Calculation of trust value for Linked Stage Graph took 7.867813110351562e-06s
INFO | --- Analysis for slod took 3.771211624145508s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 5.4836273193359375e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.27079272270202637s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.020836353302001953s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0008306503295898438s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 7.152557373046875e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 3.347748279571533s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 1.416245937347412s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0003151893615722656s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 112.97853422164917s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9729874134063721s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 8.249928712844849s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 15.569158554077148s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.2195951938629s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.9999678134918213s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.2262721061706543s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 9.628915071487427s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.21963214874267578s
License | MR license check for Smart Points Of Interest @PSNC took 0.4860384464263916s
License | HR license check for Smart Points Of Interest @PSNC took 300.2459497451782s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.3221018314361572s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.711533546447754s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.7307932376861572s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.4347515106201172s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.21909713745117188s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.2585911750793457s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.380018949508667s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 8.535385131835938e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.21103453636169434s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.19767189025878906s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.43627238273620605s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4458470344543457s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 5.575666666030884s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.49503588676452637s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.22121000289916992s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 151.11049008369446s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.18631601333618164s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.33896946907043457s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.363037109375s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 44.30156064033508s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.682023525238037s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.6198651790618896s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.17645549774169922s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 81.22922682762146s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.595181703567505s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 34.6837215423584s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.3426897525787354s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 84.0419933795929s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7896440029144287s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.63857102394104s
Security | Sign check for Smart Points Of Interest @PSNC took 0.83699631690979s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 10.11311960220337s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 1.0531792640686035s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.020894527435302734s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00011229515075683594s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Smart_POI_dataset took 2251.6317794322968s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.178726434707642s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.7574093341827393s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.600120544433594e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.1920928955078125e-05s
INFO | --- Analysis for smartlink took 14.329798221588135s
Availability | SPARQL endpoint availability check for SNIK took 0.4330160617828369s
Availability | VoID file availability check for SNIK took 0.0006897449493408203s
Extra | Recovery of all triples for SNIK took 7.890351057052612s
Performance | Total latancy measurement for SNIK took 0.9396562576293945s
Amount of data | Number of triples check for SNIK took 0.19671392440795898s
Interoperability | New terms check for SNIK took 1.484567642211914s
Versatility | Languages check for SNIK took 0.24576544761657715s
Interpretability | Number of blank nodes check for SNIK took 0.18540191650390625s
Interpretability | RDF structures check for SNIK took 0.20848369598388672s
Versatility | Serialization formats check for SNIK took 0.20859289169311523s
Availability | RDF dump link check for SNIK took 0.19692444801330566s
License | MR license check for SNIK took 0.1973578929901123s
License | HR license check for SNIK took 0.2326052188873291s
Amount of data | Number of property check for SNIK took 0.2080857753753662s
Understandability | Number of label check for SNIK took 0.19908714294433594s
Understandability | URI regex check for SNIK took 0.3911936283111572s
Understandability | Vocabs check for SNIK took 0.19695043563842773s
Verifiability | Authors check for SNIK took 0.19692611694335938s
Verifiability | Publishers check for SNIK took 0.19509053230285645s
Performance | Throughput check for SNIK took 10.932673215866089s
Amount of data | Check the number of entities for SNIK took 6.914138793945312e-05s
Verifiability | Contribs. check for SNIK took 0.1854240894317627s
Interlinking | sameAs chians check for SNIK took 0.18427562713623047s
Interlinking | skos check for SNIK took 0.1977219581604004s
Interlinking | skos check for SNIK took 0.19712471961975098s
Timeliness | dataset update frequency check for SNIK took 0.20799827575683594s
Currency | Creation date check for SNIK took 0.4038524627685547s
Currency | Modification date check for SNIK took 0.4051051139831543s
Rep.Conc. | URIs length for SNIK took 1.9893598556518555s
Interoperability | New vocabularies check for SNIK took 5.4836273193359375e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.19542360305786133s
Accuracy | Check Functional Property for SNIK took 0.1848468780517578s
Accuracy | Check Inverse Functional Property for SNIK took 0.19631195068359375s
Accuracy | Check Empty annotation labels for SNIK took 0.7999985218048096s
Accuracy | Check White space in annotation for SNIK took 0.02779388427734375s
Accuracy | Check Datatype consistency for SNIK took 0.21571779251098633s
Consistency | Disjoint class check for SNIK took 0.19594383239746094s
Consistency | Check Misplaced properties for SNIK took 0.6697039604187012s
Consistency | Misplaced classes for SNIK took 0.6931264400482178s
Consistency | Check Ontology hijacking for SNIK took 1.8733487129211426s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.242241382598877s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.508498191833496s
Conciseness | Check Extensional conciseness for SNIK took 0.1488959789276123s
Conciseness | Check Intensional conciseness for SNIK took 0.32529735565185547s
Security | Sign check for SNIK took 0.1946709156036377s
Availability | Check URIs Dereferenciability for SNIK took 786.9621679782867s
Completeness | Calculation of interlinking completeness for SNIK took 0.4617002010345459s
Reputation | Calculation of the PageRank for SNIK took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for SNIK took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for SNIK took 8.416175842285156e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 9.5367431640625e-07s
Believability | Calculation of trust value for SNIK took 7.152557373046875e-06s
INFO | --- Analysis for snik took 845.33647108078s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.1961669921875e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00035643577575683594s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.6847050189971924s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 2.9802322387695312e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 7.152557373046875e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 4.2235939502716064s
Availability | SPARQL endpoint availability check for SocialLink took 1.557676076889038s
Availability | VoID file availability check for SocialLink took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for SocialLink took 0.27083325386047363s
Reputation | Calculation of the PageRank for SocialLink took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.510185241699219e-05s
Believability | Calculation of trust value for SocialLink took 6.9141387939453125e-06s
INFO | --- Analysis for SocialLink took 9.228487730026245s
Availability | SPARQL endpoint availability check for SocialLink took 4.124641418457031e-05s
Availability | VoID file availability check for SocialLink took 0.0003104209899902344s
Completeness | Calculation of interlinking completeness for SocialLink took 0.23832917213439941s
Reputation | Calculation of the PageRank for SocialLink took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for SocialLink took 2.8848648071289062e-05s
Believability | Calculation of trust value for SocialLink took 8.344650268554688e-06s
INFO | --- Analysis for sociallink took 2.93064284324646s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.3392181396484375e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.2777822017669678s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.0040740966796875e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 7.867813110351562e-06s
INFO | --- Analysis for SocialRoles took 11.256686210632324s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.25652050971984863s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0008261203765869141s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 22.47298836708069s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.49295783042907715s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.22218632698059082s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.507225751876831s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.37471771240234375s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.2031235694885254s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.37665581703186035s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.14071393013000488s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.13300681114196777s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.829542875289917s
License | MR license check for Social Semantic Web Thesaurus took 0.1077725887298584s
License | HR license check for Social Semantic Web Thesaurus took 0.10593628883361816s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.1272873878479004s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.1179952621459961s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.20954322814941406s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.11418867111206055s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.13710999488830566s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.1391739845275879s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.637738227844238s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 6.723403930664062e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.148390531539917s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.11635518074035645s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.12487578392028809s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.0824742317199707s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.10200095176696777s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.1771409511566162s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.22347521781921387s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 2.359665870666504s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 7.600586652755737s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.10614657402038574s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.07668924331665039s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09909820556640625s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.5227282047271729s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012282371520996094s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.08802127838134766s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.3043522834777832s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.07832145690917969s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.2616753578186035s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.4834437370300293s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00016808509826660156s
Security | Sign check for Social Semantic Web Thesaurus took 0.0788571834564209s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 127.85596919059753s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.28536462783813477s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.369850158691406e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 4.048530578613281s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.8358230590820312e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 586.4187226295471s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.29648423194885254s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0003619194030761719s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 130.62500762939453s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9944431781768799s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.96483039855957s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 16.519701957702637s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2315528392792s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.246229887008667s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.24257111549377441s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.692004919052124s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3235623836517334s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.6798179149627686s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.19946932792664s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.34504222869873047s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.1946475505828857s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9674348831176758s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4768037796020508s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1988530158996582s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.25035572052001953s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.219475269317627s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.2479248046875e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19862151145935059s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18579792976379395s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.45079731941223145s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4531240463256836s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 5.351506948471069s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.47900867462158203s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2521553039550781s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 162.29059648513794s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1847066879272461s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2956845760345459s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2769463062286377s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 41.093446493148804s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.66498064994812s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.611992359161377s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19443893432617188s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 87.58209323883057s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.419839143753052s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 36.4762978553772s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.4032845497131348s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 82.97924733161926s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.7583491802215576s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5705783367156982s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9152181148529053s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.82268738746643s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.7316339015960693s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.021020889282226562s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.4332275390625e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.62939453125e-06s
INFO | --- Analysis for Soil_maps took 2287.106821537018s
Availability | SPARQL endpoint availability check for terrorrist ontology took 4.410743713378906e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.2738335132598877s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.02045464515686035s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.695487976074219e-05s
Believability | Calculation of trust value for terrorrist ontology took 8.106231689453125e-06s
INFO | --- Analysis for somya_omer took 3.4689085483551025s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.172325134277344e-05s
Availability | VoID file availability check for Sonclubcx took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.7103955745697021s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020628690719604492s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.4543533325195312e-05s
Believability | Calculation of trust value for Sonclubcx took 6.67572021484375e-06s
INFO | --- Analysis for sonclubcx took 5.152243614196777s
Availability | SPARQL endpoint availability check for SORS took 4.9114227294921875e-05s
Availability | VoID file availability check for SORS took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for SORS took 0.25718259811401367s
Reputation | Calculation of the PageRank for SORS took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for SORS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for SORS took 4.9114227294921875e-05s
Believability | Calculation of trust value for SORS took 5.245208740234375e-06s
INFO | --- Analysis for sors took 12.49304485321045s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.1961669921875e-05s
Availability | VoID file availability check for Soudy České republiky took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.257840633392334s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 3.0517578125e-05s
Believability | Calculation of trust value for Soudy České republiky took 7.62939453125e-06s
INFO | --- Analysis for soudy--esk--republiky took 3.328451156616211s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.2438507080078125e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.2735912799835205s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020476102828979492s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.298324584960938e-05s
Believability | Calculation of trust value for southampton-ac-uk took 7.3909759521484375e-06s
INFO | --- Analysis for southampton-ac-uk took 3.654060125350952s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.305678129196167s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.26773929595947266s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.021375179290771484s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.075599670410156e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 8.106231689453125e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 10.584121942520142s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 5.984306335449219e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2623271942138672s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.298324584960938e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 7.62939453125e-06s
INFO | --- Analysis for southampton-ecs-eprints took 4.241810321807861s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5833520889282227s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0002465248107910156s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 222.67681622505188s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.7882094383239746s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 9.377434730529785s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.02323055267334s
Versatility | Languages check for Spanish Linguistic Datasets took 44.830026626586914s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.1953167915344238s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.14463067054748535s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.300213098526001s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.2771482467651367s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.29149484634399414s
License | MR license check for Spanish Linguistic Datasets took 0.279285192489624s
License | HR license check for Spanish Linguistic Datasets took 0.3795967102050781s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.28883814811706543s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.31864309310913086s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5695822238922119s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.29570436477661133s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.28966450691223145s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.2861969470977783s
Performance | Throughput check for Spanish Linguistic Datasets took 11.252338171005249s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 6.771087646484375e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.2706747055053711s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.2692837715148926s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2999720573425293s
Interlinking | skos check for Spanish Linguistic Datasets took 0.20390653610229492s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.2814173698425293s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5638008117675781s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5782089233398438s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 79.16316080093384s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.28760862350463867s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.29006075859069824s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.28296613693237305s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 1.0133628845214844s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010092735290527344s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.7840349674224854s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.2886850833892822s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.767781019210815s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.568268060684204s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 70.38611006736755s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.4733569622039795s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.706741809844971s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.8828086853027344s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.2897911071777344s
Security | Sign check for Spanish Linguistic Datasets took 0.29584765434265137s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 12.447596788406372s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.39143872261047363s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021146297454833984s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.457069396972656e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.1457672119140625e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 534.1171371936798s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.07848381996154785s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2819254398345947s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.696846008300781e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 6.9141387939453125e-06s
INFO | --- Analysis for sparql-endpoint-status took 3.402461528778076s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 4.100799560546875e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.4307377338409424s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 3.2901763916015625e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 6.9141387939453125e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 3.0815589427948s
Availability | SPARQL endpoint availability check for SPQR took 4.100799560546875e-05s
Availability | VoID file availability check for SPQR took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for SPQR took 0.2789328098297119s
Reputation | Calculation of the PageRank for SPQR took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for SPQR took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for SPQR took 3.123283386230469e-05s
Believability | Calculation of trust value for SPQR took 1.239776611328125e-05s
INFO | --- Analysis for spqr took 2.9805643558502197s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.3392181396484375e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.2772643566131592s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020837068557739258s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.58306884765625e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 5.9604644775390625e-06s
INFO | --- Analysis for springernaturescigraph took 2.939335584640503s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.5299530029296875e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.2832520008087158s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0008366107940673828s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.337860107421875e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 7.867813110351562e-06s
INFO | --- Analysis for srcmf took 6.4122796058654785s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.604433536529541s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.2770233154296875s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 4.76837158203125e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 7.3909759521484375e-06s
INFO | --- Analysis for ssf took 3.8150274753570557s
Availability | SPARQL endpoint availability check for SSF took 5.221366882324219e-05s
Availability | VoID file availability check for SSF took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for SSF took 0.26152944564819336s
Reputation | Calculation of the PageRank for SSF took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for SSF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SSF took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for SSF took 3.0040740966796875e-05s
Believability | Calculation of trust value for SSF took 7.152557373046875e-06s
INFO | --- Analysis for ssf-lexicon took 2.9370579719543457s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.482269287109375e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.25804877281188965s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.647804260253906e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 6.67572021484375e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.7280941009521484s
Availability | SPARQL endpoint availability check for STAC took 4.1484832763671875e-05s
Availability | VoID file availability check for STAC took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for STAC took 0.2581758499145508s
Reputation | Calculation of the PageRank for STAC took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for STAC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for STAC took 3.0040740966796875e-05s
Believability | Calculation of trust value for STAC took 5.9604644775390625e-06s
INFO | --- Analysis for stac took 2.828920841217041s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.38690185546875e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.27263784408569336s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.0517578125e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 7.867813110351562e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.983243703842163s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.363059997558594e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.27765703201293945s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.6716461181640625e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.291534423828125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 4.237757682800293s
Availability | SPARQL endpoint availability check for Stammbuch took 4.220008850097656e-05s
Availability | VoID file availability check for Stammbuch took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2772674560546875s
Reputation | Calculation of the PageRank for Stammbuch took 0.020761966705322266s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.1948089599609375e-05s
Believability | Calculation of trust value for Stammbuch took 5.9604644775390625e-06s
INFO | --- Analysis for Stammbuch took 2.4912803173065186s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.2752597332000732s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0009310245513916016s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2655782699584961s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010633468627929688s
Believability | Calculation of trust value for statistics.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for statistics-data-gov-uk took 3.9291529655456543s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.267692565917969e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.23965167999267578s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 3.147125244140625e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 6.67572021484375e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.9112939834594727s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 5.7220458984375e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2566373348236084s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020964860916137695s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.0001049041748046875s
Believability | Calculation of trust value for statusnet-1w6-org took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-1w6-org took 2.9233598709106445s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 5.602836608886719e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2652623653411865s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 7.009506225585938e-05s
Believability | Calculation of trust value for statusnet-20100-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-20100-org took 2.452523946762085s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 5.602836608886719e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2710239887237549s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.009506225585938e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.7521235942840576s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.2534327507019043s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.20159912109375e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.4417922496795654s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.25887393951416016s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.02080368995666504s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.393692016601562e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.4833240509033203s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.2645549774169922s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011444091796875s
Believability | Calculation of trust value for statusnet-bka-li took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-bka-li took 2.489975929260254s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.2985057830810547s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020865201950073242s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.029273986816406e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.664022922515869s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.27782273292541504s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.021010160446166992s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.245208740234375e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-ced117-net took 3.8918683528900146s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.26462364196777344s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.340576171875e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.5668036937713623s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 6.842613220214844e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.27159905433654785s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020795583724975586s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011515617370605469s
Believability | Calculation of trust value for statusnet-chromic-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.577235221862793s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.26334381103515625s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.416175842285156e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.959954738616943s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2654914855957031s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.4353187084198s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.27518343925476074s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020919084548950195s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.081031799316406e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.186497211456299s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 5.507469177246094e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2602996826171875s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.021037817001342773s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010275840759277344s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.611281394958496s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.25301480293273926s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.3910622596740723s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 5.507469177246094e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2682623863220215s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.412101745605469e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.3509955406188965s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2542104721069336s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-dtdns-net took 22.354312896728516s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.25482773780822754s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020955562591552734s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.6716461181640625e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.4125590324401855s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.2626636028289795s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.43865966796875e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.43901515007019s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.26848840713500977s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 0.00010347366333007812s
Believability | Calculation of trust value for statusnet-fcac-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.375486850738525s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2538621425628662s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020913362503051758s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.1069517135620117s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.27660703659057617s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.0001819133758544922s
Believability | Calculation of trust value for statusnet-fragdev-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.350584030151367s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.2523987293243408s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.02055501937866211s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.653236389160156e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-freelish-us took 2.4495670795440674s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.2522573471069336s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.02088785171508789s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010514259338378906s
Believability | Calculation of trust value for statusnet-gegeweb-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.561505079269409s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.2558145523071289s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0008785724639892578s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.295608520507812e-05s
Believability | Calculation of trust value for statusnet-glou-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-glou-org took 2.5313057899475098s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.25050783157348633s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.021498680114746094s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.0001239776611328125s
Believability | Calculation of trust value for statusnet-gomertronic-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.4216487407684326s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2796170711517334s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010633468627929688s
Believability | Calculation of trust value for statusnet-hackerposse-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.9502112865448s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0012187957763671875s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.28635239601135254s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.553794860839844e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-hii-co-il took 3.606991767883301s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.268007755279541s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.021950960159301758s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 0.00011515617370605469s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.3946590423583984s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 5.626678466796875e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.27268171310424805s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.6494529247283936s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.696846008300781e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2733035087585449s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.02220630645751953s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0011098384857177734s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 5.0067901611328125e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.6297523975372314s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2625303268432617s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 7.62939453125e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.396599769592285s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.28040623664855957s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020684003829956055s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011491775512695312s
Believability | Calculation of trust value for statusnet-jonkman-ca took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.410578489303589s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2520577907562256s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.021339893341064453s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0011665821075439453s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 0.00011420249938964844s
Believability | Calculation of trust value for statusnet-kaimi-cc took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.4173808097839355s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2651052474975586s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0010519027709960938s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.42145037651062s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.24176907539367676s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.673004150390625e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.2427051067352295s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.2791779041290283s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020859956741333008s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.486343383789062e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.3314425945281982s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 7.152557373046875e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.26653242111206055s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02153944969177246s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.935264587402344e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.4664103984832764s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2687671184539795s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.619161367416382s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.27976250648498535s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.655952453613281e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.588212490081787s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.27503514289855957s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020931005477905273s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011706352233886719s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.4028236865997314s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 5.602836608886719e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.26216721534729004s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.021536588668823242s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.888938903808594e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.7422969341278076s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2561650276184082s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020964860916137695s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.00010085105895996094s
Believability | Calculation of trust value for statusnet-lydiastench-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.3643128871917725s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 5.269050598144531e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2459700107574463s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.2724673748016357s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2431025505065918s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020988941192626953s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.0001666545867919922s
Believability | Calculation of trust value for statusnet-macno-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-macno-org took 2.3910179138183594s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.26442885398864746s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.914138793945312e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.4978790283203125s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.3252885341644287s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.034706115722656e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.30921745300293s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 5.364418029785156e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2532539367675781s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.0001583099365234375s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.387847661972046s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.2729651927947998s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.00010609626770019531s
Believability | Calculation of trust value for statusnet-mrblog-nl took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.5607879161834717s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 6.29425048828125e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.24642562866210938s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.245208740234375e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.378868818283081s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 7.677078247070312e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.24985790252685547s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.6046712398529053s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 5.245208740234375e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2621593475341797s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.021784305572509766s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.001051187515258789s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.0001361370086669922s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.6226391792297363s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2764160633087158s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.021390199661254883s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0010957717895507812s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 7.176399230957031e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.6149721145629883s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.2671017646789551s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0009548664093017578s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 7.224082946777344e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.520803689956665s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.29201436042785645s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.559226989746094e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.928544521331787s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.29691267013549805s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.8160552978515625e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-panda-id-au took 3.006420612335205s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.26128220558166504s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.465217590332031e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.452789306640625s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.271557092666626s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.653236389160156e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.3930325508117676s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.25170159339904785s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.02093219757080078s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0009667873382568359s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00024962425231933594s
Believability | Calculation of trust value for statusnet-postblue-info took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.4008450508117676s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.25205183029174805s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0010089874267578125s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.557868957519531e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-progval-net took 2.441683530807495s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.29041075706481934s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.021706104278564453s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.001056671142578125s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00012874603271484375s
Believability | Calculation of trust value for statusnet-qdnx-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.932176113128662s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2925245761871338s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.231863021850586s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.25737810134887695s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021767616271972656s
Believability | Calculation of trust value for statusnet-quitter-se took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.5361201763153076s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 5.14984130859375e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0011186599731445312s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.2713627815246582s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010275840759277344s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.5381064414978027s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.25859570503234863s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020163774490356445s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-recit-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-recit-org took 4.84924840927124s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.26181983947753906s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001461505889892578s
Believability | Calculation of trust value for statusnet-russwurm-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-russwurm-org took 3.155900478363037s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.27906203269958496s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.02179408073425293s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 4.100799560546875e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0010714530944824219s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 9.655952453613281e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-samnoble-org took 4.829480886459351s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.001163482666015625s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2587261199951172s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.058547973632812e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.582974433898926s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.26490211486816406s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.655952453613281e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.4513158798217773s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 5.2928924560546875e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.001094818115234375s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.24758124351501465s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020273208618164062s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.402480363845825s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.25049543380737305s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.176399230957031e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.338285446166992s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.2618732452392578s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.02016472816467285s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00023102760314941406s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 2.9489500522613525s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.25984930992126465s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00011181831359863281s
Believability | Calculation of trust value for statusnet-somsants-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.415168046951294s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.26090407371520996s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0009064674377441406s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00014925003051757812s
Believability | Calculation of trust value for statusnet-soucy-cc took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.390069007873535s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.26575350761413574s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020272254943847656s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-spip-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-spip-org took 3.4039151668548584s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2684359550476074s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020227432250976562s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.246566772460938e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.4487650394439697s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.001394033432006836s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.26142215728759766s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00011491775512695312s
Believability | Calculation of trust value for statusnet-ssweeny-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.532407760620117s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.25600385665893555s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022602081298828125s
Believability | Calculation of trust value for statusnet-status-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-status-net took 3.5092108249664307s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 8.130073547363281e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2767155170440674s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0009887218475341797s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.3712825775146484s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.27403807640075684s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 8.869171142578125e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.493152141571045s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.28647303581237793s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001239776611328125s
Believability | Calculation of trust value for statusnet-thelovebug-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.6861143112182617s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2660503387451172s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.414817810058594e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-thornton2-com took 5.008844375610352s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 5.078315734863281e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.2728750705718994s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.021175384521484375s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.0001342296600341797s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.768190860748291s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 5.269050598144531e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2842385768890381s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.022228002548217773s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.172325134277344e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.5471901893615723s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.744529724121094e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2777247428894043s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 7.152557373046875e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.706169366836548s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2626810073852539s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020807981491088867s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 4.1484832763671875e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.5752928256988525s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.673004150390625e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.25759458541870117s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.218650817871094e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 6.198883056640625e-06s
INFO | --- Analysis for steak took 2.625821828842163s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.363059997558594e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.2805135250091553s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.14984130859375e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 6.9141387939453125e-06s
INFO | --- Analysis for stitch-rameau took 4.000011682510376s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.9938235282897949s
Availability | VoID file availability check for Stone Tech Square took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.2640984058380127s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.239776611328125e-05s
Believability | Calculation of trust value for Stone Tech Square took 6.67572021484375e-06s
INFO | --- Analysis for stone-tech-square-data took 4.89349889755249s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 5.1021575927734375e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.2766909599304199s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 2.765655517578125e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 7.3909759521484375e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.871009588241577s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.44667506217956543s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0003540515899658203s
Extra | Recovery of all triples for STW Thesaurus for Economics took 40.338093757629395s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.1425776481628418s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6039047241210938s
Interoperability | New terms check for STW Thesaurus for Economics took 1.5707223415374756s
Versatility | Languages check for STW Thesaurus for Economics took 1.4440557956695557s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.4633369445800781s
Security | Check HTTPS for STW Thesaurus for Economics took 0.1406543254852295s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2739133834838867s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.28066062927246094s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.2519516944885254s
License | MR license check for STW Thesaurus for Economics took 0.2599959373474121s
License | HR license check for STW Thesaurus for Economics took 2.1894352436065674s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.27207136154174805s
Understandability | Number of label check for STW Thesaurus for Economics took 0.7044932842254639s
Understandability | URI regex check for STW Thesaurus for Economics took 0.47861337661743164s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.28104400634765625s
Verifiability | Authors check for STW Thesaurus for Economics took 0.25347900390625s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.2447826862335205s
Performance | Throughput check for STW Thesaurus for Economics took 11.0187087059021s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7423620223999023s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.25438714027404785s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.2886021137237549s
Interlinking | skos check for STW Thesaurus for Economics took 0.33892059326171875s
Interlinking | skos check for STW Thesaurus for Economics took 0.2990117073059082s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.23345065116882324s
Currency | Creation date check for STW Thesaurus for Economics took 0.5308969020843506s
Currency | Modification date check for STW Thesaurus for Economics took 0.5096437931060791s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 9.594953775405884s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 18.02672004699707s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.250227689743042s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2857785224914551s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.2651996612548828s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 11.105087757110596s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0553529262542725s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.4360790252685547s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.2630949020385742s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.1732127666473389s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 2.510709762573242s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.3776133060455322s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.342616081237793s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.686797857284546s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2821695804595947s
Security | Sign check for STW Thesaurus for Economics took 0.2584562301635742s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 3886.6015112400055s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 1.6713299751281738s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00012373924255371094s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 21.081867694854736s
Believability | Calculation of trust value for STW Thesaurus for Economics took 7.3909759521484375e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 4050.9160237312317s
Availability | SPARQL endpoint availability check for SudershanTech took 4.410743713378906e-05s
Availability | VoID file availability check for SudershanTech took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.2971336841583252s
Reputation | Calculation of the PageRank for SudershanTech took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.0517578125e-05s
Believability | Calculation of trust value for SudershanTech took 7.62939453125e-06s
INFO | --- Analysis for SudershanTech took 3.3942790031433105s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.8862035274505615s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0003960132598876953s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.2561452388763428s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.8160552978515625e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 7.3909759521484375e-06s
INFO | --- Analysis for sudocfr took 6.971150636672974s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0028645992279053s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006589889526367188s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 289.8167757987976s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.7040839195251465s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.715590476989746s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 3.151912212371826s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.0595479011535645s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.3377842903137207s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5744867324829102s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5294208526611328s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.577195405960083s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5653073787689209s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 8.031999588012695s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5963640213012695s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.6874270439147949s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.0768630504608154s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5708198547363281s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5807697772979736s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5146951675415039s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.980313062667847s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 7.748603820800781e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5528981685638428s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5677545070648193s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6319582462310791s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5911877155303955s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5619919300079346s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.1265854835510254s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.081472635269165s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 79.97156167030334s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5449259281158447s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5633783340454102s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5408289432525635s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 14.8168306350708s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.378964900970459s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5567915439605713s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 35.54337239265442s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.985080242156982s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.42206597328186s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 26.24126648902893s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.051142692565918s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 4.129261016845703s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5496063232421875s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4690.521740913391s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 1.1489155292510986s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 9.107589721679688e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 2.384185791015625e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 9.059906005859375e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8638.221485376358s
Availability | SPARQL endpoint availability check for Surge Radio took 4.57763671875e-05s
Availability | VoID file availability check for Surge Radio took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.6858158111572266s
Reputation | Calculation of the PageRank for Surge Radio took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.440017700195312e-05s
Believability | Calculation of trust value for Surge Radio took 7.152557373046875e-06s
INFO | --- Analysis for surge-radio took 5.121603488922119s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.315376281738281e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.2809467315673828s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 2.9087066650390625e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 7.152557373046875e-06s
INFO | --- Analysis for SWAT took 20.64087963104248s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.315376281738281e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.4407038688659668s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2677145004272461s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.985664367675781e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 6.9141387939453125e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.357151508331299s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.191533088684082s
Availability | VoID file availability check for SweFN-RDF took 0.0012929439544677734s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.28734397888183594s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020162343978881836s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for SweFN-RDF took 7.152557373046875e-06s
INFO | --- Analysis for swefn-rdf took 5.994966745376587s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.4345855712890625e-05s
Availability | VoID file availability check for SwetoDblp took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.25622081756591797s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020390987396240234s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.5762786865234375e-05s
Believability | Calculation of trust value for SwetoDblp took 6.9141387939453125e-06s
INFO | --- Analysis for sweto-dblp took 23.19936966896057s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.523604154586792s
Availability | VoID file availability check for Swift Vocabulary took 0.0005762577056884766s
Extra | Recovery of all triples for Swift Vocabulary took 2.159388780593872s
Performance | Total latancy measurement for Swift Vocabulary took 1.0354125499725342s
Amount of data | Number of triples check for Swift Vocabulary took 0.15740060806274414s
Interoperability | New terms check for Swift Vocabulary took 1.4053666591644287s
Versatility | Languages check for Swift Vocabulary took 0.18698978424072266s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.1708977222442627s
Interpretability | RDF structures check for Swift Vocabulary took 0.16170787811279297s
Versatility | Serialization formats check for Swift Vocabulary took 0.1938025951385498s
Availability | RDF dump link check for Swift Vocabulary took 0.17280960083007812s
License | MR license check for Swift Vocabulary took 0.1764817237854004s
License | HR license check for Swift Vocabulary took 0.18642783164978027s
Amount of data | Number of property check for Swift Vocabulary took 0.20267510414123535s
Understandability | Number of label check for Swift Vocabulary took 0.20070648193359375s
Understandability | URI regex check for Swift Vocabulary took 0.35170507431030273s
Understandability | Vocabs check for Swift Vocabulary took 0.18906235694885254s
Verifiability | Authors check for Swift Vocabulary took 0.21066761016845703s
Verifiability | Publishers check for Swift Vocabulary took 0.18096375465393066s
Performance | Throughput check for Swift Vocabulary took 10.81526803970337s
Amount of data | Check the number of entities for Swift Vocabulary took 7.319450378417969e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.21909737586975098s
Interlinking | sameAs chians check for Swift Vocabulary took 0.19189167022705078s
Interlinking | skos check for Swift Vocabulary took 0.23295044898986816s
Interlinking | skos check for Swift Vocabulary took 0.2129673957824707s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.2268538475036621s
Currency | Creation date check for Swift Vocabulary took 0.4136061668395996s
Currency | Modification date check for Swift Vocabulary took 0.4290456771850586s
Rep.Conc. | URIs length for Swift Vocabulary took 0.8133049011230469s
Interoperability | New vocabularies check for Swift Vocabulary took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.19237542152404785s
Accuracy | Check Functional Property for Swift Vocabulary took 0.17967796325683594s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.17427825927734375s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.34023046493530273s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.0019769668579101562s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03545188903808594s
Consistency | Disjoint class check for Swift Vocabulary took 0.21253466606140137s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.47093629837036133s
Consistency | Misplaced classes for Swift Vocabulary took 0.3024320602416992s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.4559149742126465s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.2636375427246094s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.4606990814208984s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.02573251724243164s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.1815495491027832s
Security | Sign check for Swift Vocabulary took 0.18911147117614746s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 991.7147300243378s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.5596294403076172s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.020723342895507812s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 7.891654968261719e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 2.384185791015625e-06s
Believability | Calculation of trust value for Swift Vocabulary took 7.867813110351562e-06s
INFO | --- Analysis for Swift took 1037.0577256679535s
Availability | SPARQL endpoint availability check for SymbolicData took 4.3392181396484375e-05s
Availability | VoID file availability check for SymbolicData took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.7104544639587402s
Reputation | Calculation of the PageRank for SymbolicData took 0.020761966705322266s
Interlinking | Calculation of Degree of Connection for SymbolicData took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.147125244140625e-05s
Believability | Calculation of trust value for SymbolicData took 7.867813110351562e-06s
INFO | --- Analysis for symbolicdata took 5.6753151416778564s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.3392181396484375e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0014843940734863281s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.2663290500640869s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 4.315376281738281e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 7.3909759521484375e-06s
INFO | --- Analysis for symptoms-in-chinese took 53.599518060684204s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.5042459964752197s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0005776882171630859s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.5083379745483398s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.90989089012146s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 50.25877094268799s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 19.181843042373657s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.17360830307006836s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 5.247875213623047s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.1118471622467041s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.67588210105896s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.6146197319030762s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.18383502960205078s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.4330110549926758s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.80862021446228s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5206711292266846s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 37.491427183151245s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3662073612213135s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.20549583435058594s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.1782221794128418s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.8344740867614746s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.653263092041016s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 6.67572021484375e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.6785988807678223s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.8219425678253174s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.6243467330932617s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5309913158416748s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.5449821949005127s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 2.982239007949829s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.881906509399414s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 67.42238116264343s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.17260265350341797s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.23978042602539062s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0011904239654541016s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0015761852264404297s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.20445513725280762s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.855555057525635s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.25963616371154785s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.5807530879974365s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3061847686767578s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.161991357803345s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002131223678588867s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.32119035720825195s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.19781136512756348s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 11.464752674102783s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.7991926670074463s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.021062374114990234s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.654594421386719e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 6.198883056640625e-06s
INFO | --- Analysis for sztaki-lod took 719.786506652832s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.76837158203125e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0007736682891845703s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.2873256206512451s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.0067901611328125e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 7.3909759521484375e-06s
INFO | --- Analysis for t4gm-info took 7.607971429824829s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.363059997558594e-05s
Availability | VoID file availability check for tags2con delicious took 0.0007812976837158203s
Completeness | Calculation of interlinking completeness for tags2con delicious took 1.288198709487915s
Reputation | Calculation of the PageRank for tags2con delicious took 0.021196365356445312s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 7.200241088867188e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.5299530029296875e-05s
Believability | Calculation of trust value for tags2con delicious took 7.62939453125e-06s
INFO | --- Analysis for tags2con-delicious took 848.2995600700378s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.83839082717896s
Availability | VoID file availability check for Taiwan geographic names took 0.0008783340454101562s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.3324143886566162s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020949840545654297s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 6.580352783203125e-05s
Believability | Calculation of trust value for Taiwan geographic names took 7.62939453125e-06s
INFO | --- Analysis for taiwan-geographic-names took 670.4480855464935s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 5.221366882324219e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.7046172618865967s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.023235082626342773s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0010831356048583984s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 0.00011706352233886719s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 7.3909759521484375e-06s
INFO | --- Analysis for talis-openlibrary took 8.212926149368286s
Availability | SPARQL endpoint availability check for TalkBank took 4.1961669921875e-05s
Availability | VoID file availability check for TalkBank took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for TalkBank took 0.27084946632385254s
Reputation | Calculation of the PageRank for TalkBank took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for TalkBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TalkBank took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.8848648071289062e-05s
Believability | Calculation of trust value for TalkBank took 7.3909759521484375e-06s
INFO | --- Analysis for talkbank took 3.033064603805542s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.9711627960205078s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.977473258972168s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00012087821960449219s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 7.3909759521484375e-06s
INFO | --- Analysis for taxonconcept took 15.947067499160767s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 5.698204040527344e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.37656545639038086s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.021471023559570312s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 9.322166442871094e-05s
Believability | Calculation of trust value for taxonconcept-assets took 7.62939453125e-06s
INFO | --- Analysis for taxonconcept-assets took 3.5278842449188232s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 5.412101745605469e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.26688599586486816s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.316734313964844e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 7.867813110351562e-06s
INFO | --- Analysis for taxonconcept-occurences took 3.2380528450012207s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 1.4216499328613281s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.2713286876678467s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 6.008148193359375e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 8.821487426757812e-06s
INFO | --- Analysis for taxref-ld took 29.05489468574524s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 261.6422600746155s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.30632638931274414s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.023810386657714844s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0009553432464599609s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.267692565917969e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 8.344650268554688e-06s
INFO | --- Analysis for tcga took 540.119292974472s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3700387477874756s
Availability | VoID file availability check for TCGA Roadmap took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.6974279880523682s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.021046876907348633s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 8.678436279296875e-05s
Believability | Calculation of trust value for TCGA Roadmap took 7.867813110351562e-06s
INFO | --- Analysis for tcga-roadmap took 7.388577938079834s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 4.079802513122559s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.39156126976013184s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010395050048828125s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 7.62939453125e-06s
INFO | --- Analysis for tcmgenedit_dataset took 143.2766044139862s
Availability | SPARQL endpoint availability check for TDS took 4.315376281738281e-05s
Availability | VoID file availability check for TDS took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for TDS took 0.2655446529388428s
Reputation | Calculation of the PageRank for TDS took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for TDS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for TDS took 4.506111145019531e-05s
Believability | Calculation of trust value for TDS took 7.152557373046875e-06s
INFO | --- Analysis for tds took 34.683926582336426s
Availability | SPARQL endpoint availability check for TED Talks took 5.054473876953125e-05s
Availability | VoID file availability check for TED Talks took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for TED Talks took 0.31473493576049805s
Reputation | Calculation of the PageRank for TED Talks took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for TED Talks took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TED Talks took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for TED Talks took 2.9087066650390625e-05s
Believability | Calculation of trust value for TED Talks took 6.4373016357421875e-06s
INFO | --- Analysis for ted-talks took 3.908186435699463s
Availability | SPARQL endpoint availability check for TEKORD took 4.553794860839844e-05s
Availability | VoID file availability check for TEKORD took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2898681163787842s
Reputation | Calculation of the PageRank for TEKORD took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.601478576660156e-05s
Believability | Calculation of trust value for TEKORD took 7.3909759521484375e-06s
INFO | --- Analysis for tekord took 5.568052768707275s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 1.8288729190826416s
Availability | VoID file availability check for Telegraphis Linked Data took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.24837994575500488s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00011610984802246094s
Believability | Calculation of trust value for Telegraphis Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for telegraphis took 8.053167343139648s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.3392181396484375e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.25815248489379883s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.05718994140625e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 6.67572021484375e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 14.314950466156006s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.2780578136444092s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.0040740966796875e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.9896745681762695s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.3392181396484375e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2820558547973633s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 3.337860107421875e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 1.4066696166992188e-05s
INFO | --- Analysis for terminesp took 3.0363736152648926s
Availability | SPARQL endpoint availability check for Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for Ontology took 0.24834656715393066s
Reputation | Calculation of the PageRank for Ontology took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Ontology took 7.152557373046875e-06s
INFO | --- Analysis for Terrorist_attack took 3.0615456104278564s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.7206878662109375e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.30164575576782227s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.24249267578125e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 8.344650268554688e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.5135176181793213s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 5.125999450683594e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.2925417423248291s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020758390426635742s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 3.695487976074219e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.62939453125e-06s
INFO | --- Analysis for tesauro-materias-bupm took 3.2692549228668213s
Availability | SPARQL endpoint availability check for Teseo took 5.364418029785156e-05s
Availability | VoID file availability check for Teseo took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Teseo took 0.33842039108276367s
Reputation | Calculation of the PageRank for Teseo took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Teseo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0008218288421630859s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.123283386230469e-05s
Believability | Calculation of trust value for Teseo took 7.62939453125e-06s
INFO | --- Analysis for teseo took 3.0174429416656494s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 8.106231689453125e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.2647886276245117s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020798206329345703s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.266334533691406e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 8.344650268554688e-06s
INFO | --- Analysis for Tesla_Deaths took 4.681167125701904s
Availability | SPARQL endpoint availability check for test took 4.291534423828125e-05s
Availability | VoID file availability check for test took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for test took 0.28976893424987793s
Reputation | Calculation of the PageRank for test took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for test took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for test took 5.245208740234375e-05s
Believability | Calculation of trust value for test took 7.62939453125e-06s
INFO | --- Analysis for test took 2.470926523208618s
Availability | SPARQL endpoint availability check for Test took 4.7206878662109375e-05s
Availability | VoID file availability check for Test took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Test took 0.28308749198913574s
Reputation | Calculation of the PageRank for Test took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Test took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Test took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Test took 3.218650817871094e-05s
Believability | Calculation of trust value for Test took 7.62939453125e-06s
INFO | --- Analysis for Test took 2.4203758239746094s
Availability | SPARQL endpoint availability check for test-svu took 20.215956926345825s
Availability | VoID file availability check for test-svu took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for test-svu took 0.2596890926361084s
Reputation | Calculation of the PageRank for test-svu took 0.020305871963500977s
Interlinking | Calculation of Degree of Connection for test-svu took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for test-svu took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for test-svu took 2.86102294921875e-05s
Believability | Calculation of trust value for test-svu took 7.152557373046875e-06s
INFO | --- Analysis for test-svu took 52.670029640197754s
Availability | SPARQL endpoint availability check for Test took 4.363059997558594e-05s
Availability | VoID file availability check for Test took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Test took 0.2547292709350586s
Reputation | Calculation of the PageRank for Test took 0.020951271057128906s
Interlinking | Calculation of Degree of Connection for Test took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Test took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Test took 2.86102294921875e-05s
Believability | Calculation of trust value for Test took 7.152557373046875e-06s
INFO | --- Analysis for Test_ took 2.8383734226226807s
Availability | SPARQL endpoint availability check for xxxxx took 261.81491017341614s
Availability | VoID file availability check for xxxxx took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for xxxxx took 0.4164083003997803s
Reputation | Calculation of the PageRank for xxxxx took 0.020944595336914062s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for xxxxx took 5.6743621826171875e-05s
Believability | Calculation of trust value for xxxxx took 7.3909759521484375e-06s
INFO | --- Analysis for testee took 798.9377865791321s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.2438507080078125e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.2800428867340088s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.0994415283203125e-05s
Believability | Calculation of trust value for Texai Lexicon took 8.106231689453125e-06s
INFO | --- Analysis for texai_lexicon took 4.821952819824219s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.315376281738281e-05s
Availability | VoID file availability check for tharawat magazine took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.25522661209106445s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02035069465637207s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010824203491210938s
Believability | Calculation of trust value for tharawat magazine took 7.62939453125e-06s
INFO | --- Analysis for tharawat-magazine-com took 4.4710540771484375s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.1484832763671875e-05s
Availability | VoID file availability check for The CIARD RING took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.24708890914916992s
Reputation | Calculation of the PageRank for The CIARD RING took 0.020345211029052734s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.0517578125e-05s
Believability | Calculation of trust value for The CIARD RING took 7.62939453125e-06s
INFO | --- Analysis for the-ciard-ring took 3.7647645473480225s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.15185880661010742s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.24849581718444824s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.147125244140625e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 3.0517578125e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.733551263809204s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.9087257385253906s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007143020629882812s
Extra | Recovery of all triples for The European Library Open Dataset took 1.4355041980743408s
Performance | Total latancy measurement for The European Library Open Dataset took 1.2953317165374756s
Amount of data | Number of triples check for The European Library Open Dataset took 30.212308168411255s
Versatility | Languages check for The European Library Open Dataset took 0.3151853084564209s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.222808361053467s
Interpretability | RDF structures check for The European Library Open Dataset took 0.27790236473083496s
Versatility | Serialization formats check for The European Library Open Dataset took 0.2657134532928467s
Availability | RDF dump link check for The European Library Open Dataset took 0.2513720989227295s
License | MR license check for The European Library Open Dataset took 0.2873518466949463s
License | HR license check for The European Library Open Dataset took 0.27168893814086914s
Amount of data | Number of property check for The European Library Open Dataset took 0.29850268363952637s
Understandability | Number of label check for The European Library Open Dataset took 1.2360401153564453s
Understandability | URI regex check for The European Library Open Dataset took 0.6145222187042236s
Understandability | Vocabs check for The European Library Open Dataset took 0.24071502685546875s
Verifiability | Authors check for The European Library Open Dataset took 0.26973438262939453s
Verifiability | Publishers check for The European Library Open Dataset took 0.27292895317077637s
Performance | Throughput check for The European Library Open Dataset took 11.277872800827026s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.414817810058594e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.22790980339050293s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.2926614284515381s
Interlinking | skos check for The European Library Open Dataset took 0.2954726219177246s
Interlinking | skos check for The European Library Open Dataset took 0.3058030605316162s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.25458526611328125s
Currency | Creation date check for The European Library Open Dataset took 0.5420904159545898s
Currency | Modification date check for The European Library Open Dataset took 0.5141704082489014s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.483699321746826s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.276888370513916s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 1.8280961513519287s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.02788543701171875s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.027728796005249023s
Consistency | Disjoint class check for The European Library Open Dataset took 0.34901905059814453s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.50127673149109s
Consistency | Misplaced classes for The European Library Open Dataset took 0.34514641761779785s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.7631103992462158s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.2544515132904053s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.461466073989868s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.0328364372253418s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.2979085445404053s
Security | Sign check for The European Library Open Dataset took 0.29102087020874023s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 11.36830735206604s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.3628561496734619s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for the-european-library-open-dataset took 400.80288648605347s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.051949977874756s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.3125886917114258s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.021271944046020508s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0008568763732910156s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00011944770812988281s
Believability | Calculation of trust value for The Eurostat Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for the-eurostat-linked-data took 244.22262716293335s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 5.6743621826171875e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.2750418186187744s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0008454322814941406s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.266334533691406e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.62939453125e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 5.196734666824341s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.315376281738281e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.2963407039642334s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 8.249282836914062e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 7.152557373046875e-06s
INFO | --- Analysis for the-living-lod-cloud took 43.85795259475708s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 4.172325134277344e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.2604665756225586s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 2.8848648071289062e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 7.152557373046875e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.398655414581299s
Availability | SPARQL endpoint availability check for The View From took 0.06889700889587402s
Availability | VoID file availability check for The View From took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for The View From took 0.2974846363067627s
Reputation | Calculation of the PageRank for The View From took 0.02029705047607422s
Interlinking | Calculation of Degree of Connection for The View From took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The View From took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for The View From took 8.058547973632812e-05s
Believability | Calculation of trust value for The View From took 7.62939453125e-06s
INFO | --- Analysis for the-view-from took 2.5473265647888184s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.580397129058838s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.26319003105163574s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.0211489200592041s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 6.9141387939453125e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.04761266708374s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.170356273651123s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.40394020080566406s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 4.076957702636719e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 8.106231689453125e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.87136101722717s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.3392181396484375e-05s
Availability | VoID file availability check for The Content Wrangler took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.2457447052001953s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010609626770019531s
Believability | Calculation of trust value for The Content Wrangler took 7.152557373046875e-06s
INFO | --- Analysis for thecontentwrangler-com took 2.877241849899292s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.100799560546875e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.2618849277496338s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.075599670410156e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 7.867813110351562e-06s
INFO | --- Analysis for thesaurus-bncf took 2.9878756999969482s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.482269287109375e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2663838863372803s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.075599670410156e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 8.344650268554688e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.979180097579956s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 8.811688899993896s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.2478318214416504s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.772445678710938e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 8.344650268554688e-06s
INFO | --- Analysis for thesaurus-w took 14.940443754196167s
Availability | SPARQL endpoint availability check for theses.fr took 4.3392181396484375e-05s
Availability | VoID file availability check for theses.fr took 0.0003325939178466797s
Completeness | Calculation of interlinking completeness for theses.fr took 0.29466891288757324s
Reputation | Calculation of the PageRank for theses.fr took 0.02145242691040039s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.125999450683594e-05s
Believability | Calculation of trust value for theses.fr took 8.106231689453125e-06s
INFO | --- Analysis for thesesfr took 4.194356679916382s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 5.412101745605469e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.2829570770263672s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.62396240234375e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 6.9141387939453125e-06s
INFO | --- Analysis for Thinkphile took 2.4658634662628174s
Availability | SPARQL endpoint availability check for ThIST took 264.8357346057892s
Availability | VoID file availability check for ThIST took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for ThIST took 0.24728798866271973s
Reputation | Calculation of the PageRank for ThIST took 0.020842552185058594s
Interlinking | Calculation of Degree of Connection for ThIST took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.226799011230469e-05s
Believability | Calculation of trust value for ThIST took 7.867813110351562e-06s
INFO | --- Analysis for thist took 562.9867680072784s
Availability | SPARQL endpoint availability check for TIP took 40.04106664657593s
Availability | VoID file availability check for TIP took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for TIP took 0.2691633701324463s
Reputation | Calculation of the PageRank for TIP took 0.020951509475708008s
Interlinking | Calculation of Degree of Connection for TIP took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011873245239257812s
Believability | Calculation of trust value for TIP took 6.67572021484375e-06s
INFO | --- Analysis for tip took 103.09441137313843s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.267692565917969e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0007450580596923828s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.3056485652923584s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.02068161964416504s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.3855438232421875e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 7.152557373046875e-06s
INFO | --- Analysis for TOPMODEL took 21.130409002304077s
Availability | SPARQL endpoint availability check for Tourpedia took 4.076957702636719e-05s
Availability | VoID file availability check for Tourpedia took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.693157434463501s
Reputation | Calculation of the PageRank for Tourpedia took 0.021148681640625s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0010340213775634766s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.4809112548828125e-05s
Believability | Calculation of trust value for Tourpedia took 7.3909759521484375e-06s
INFO | --- Analysis for tourpedia took 3.842456340789795s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.4211277961730957s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.27875351905822754s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.4332275390625e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 6.67572021484375e-06s
INFO | --- Analysis for TP-data took 7.827338218688965s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 2.343165636062622s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.0006330013275146484s
Extra | Recovery of all triples for Trackloaded Linked Open Data took 1.9974865913391113s
Performance | Total latancy measurement for Trackloaded Linked Open Data took 2.1550090312957764s
Amount of data | Number of triples check for Trackloaded Linked Open Data took 2.2283132076263428s
Interoperability | New terms check for Trackloaded Linked Open Data took 3.4504523277282715s
Versatility | Languages check for Trackloaded Linked Open Data took 2.043865919113159s
Interpretability | Number of blank nodes check for Trackloaded Linked Open Data took 2.0300679206848145s
Interpretability | RDF structures check for Trackloaded Linked Open Data took 2.0664124488830566s
Versatility | Serialization formats check for Trackloaded Linked Open Data took 2.231350898742676s
Availability | RDF dump link check for Trackloaded Linked Open Data took 2.237565755844116s
License | MR license check for Trackloaded Linked Open Data took 2.0607779026031494s
License | HR license check for Trackloaded Linked Open Data took 2.1030709743499756s
Amount of data | Number of property check for Trackloaded Linked Open Data took 2.497854709625244s
Understandability | Number of label check for Trackloaded Linked Open Data took 1.9868721961975098s
Understandability | URI regex check for Trackloaded Linked Open Data took 4.098884105682373s
Understandability | Vocabs check for Trackloaded Linked Open Data took 2.2269983291625977s
Verifiability | Authors check for Trackloaded Linked Open Data took 3.0692825317382812s
Verifiability | Publishers check for Trackloaded Linked Open Data took 2.4265663623809814s
Performance | Throughput check for Trackloaded Linked Open Data took 32.56193423271179s
Amount of data | Check the number of entities for Trackloaded Linked Open Data took 8.440017700195312e-05s
Verifiability | Contribs. check for Trackloaded Linked Open Data took 9.817474842071533s
Interlinking | sameAs chians check for Trackloaded Linked Open Data took 3.121354341506958s
Interlinking | skos check for Trackloaded Linked Open Data took 2.9348154067993164s
Interlinking | skos check for Trackloaded Linked Open Data took 0.0644838809967041s
Timeliness | dataset update frequency check for Trackloaded Linked Open Data took 2.7673819065093994s
Currency | Creation date check for Trackloaded Linked Open Data took 5.395055055618286s
Currency | Modification date check for Trackloaded Linked Open Data took 5.979418992996216s
Rep.Conc. | URIs length for Trackloaded Linked Open Data took 3.738591194152832s
Interoperability | New vocabularies check for Trackloaded Linked Open Data took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Linked Open Data took 0.9332742691040039s
Consistency | Disjoint class check for Trackloaded Linked Open Data took 1.0402140617370605s
Consistency | Check Ontology hijacking for Trackloaded Linked Open Data took 1.8653264045715332s
Consistency | Check Invalid usage of undefined properties for Trackloaded Linked Open Data took 4.389153242111206s
Security | Sign check for Trackloaded Linked Open Data took 1.012702465057373s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.2646067142486572s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.02092432975769043s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 2.1457672119140625e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Linked Open Data took 1.430511474609375e-06s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 7.3909759521484375e-06s
